fix(tests): migrate expect assertion messages to Vitest format #16787
+421
−435
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Vitest requires assertion messages as the second argument to
expect(), not as the last argument to matchers like Jasmine.Changes
toHaveBeenCalledWithfrom transformation (all arguments are call parameters)toBe,toEqual) and no-arg matchers (toBeDefined,toBeTruthy)Example
Implementation
Automated transformation using Python script that:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.