You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In issue #527 (comment), @hi-ogawa kindly provided an example of some code that should be possible in Vitest 2.2 and higher. Since 3.0 is the new 2.2, I thought this would apply as well.
Now run your test. If you run vitest --update from the command-line, it properly provides the value "all". If you run vitest from the command-line, it properly provides the value "new".
But if you run "Update snapshot" from VS Code (by right-clicking on a test), it always provides the value "new". So something is causing it to not display the correct value ("all").
Output
N/A for this type of issue.
Extension Version
1.10.3
Vitest Version
vitest/3.0.0 linux-arm64 node-v23.5.0
Validations
Check that you are using the latest version of the extension
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Describe the bug
In issue #527 (comment), @hi-ogawa kindly provided an example of some code that should be possible in Vitest 2.2 and higher. Since 3.0 is the new 2.2, I thought this would apply as well.
Reproduction
Use the following global setup file:
Now run your test. If you run
vitest --update
from the command-line, it properly provides the value"all"
. If you runvitest
from the command-line, it properly provides the value"new"
.But if you run "Update snapshot" from VS Code (by right-clicking on a test), it always provides the value
"new"
. So something is causing it to not display the correct value ("all"
).Output
Extension Version
1.10.3
Vitest Version
vitest/3.0.0 linux-arm64 node-v23.5.0
Validations
The text was updated successfully, but these errors were encountered: