Describe the bug
Copy Error / Copy Test Errors actions appear on non-Vitest test results.
Clicking them on another controller's results is a no-op or can show unrelated Vitest warnings.
Vitest-specific copy actions seem to leak into foreign Testing controllers/results.
Expected behavior
Those actions should only appear for Vitest-owned results/messages.
Likely fix: add proper when scoping to the result/message menu contributions.
Reproduction
- Install Vitest VS Code extension and another Testing extension, for cleaner repro I use AlexChexes.tmgrammar-test-tools-vscode which works on unsaved files.
- Open a new VS Code window without any Vitest project or test files.
- Open a new tab with a trivial test, for example:
// SYNTAX TEST "source.js"
foo = 42
// ^^ constant.numeric.decimal.js
- Run the test from the non-Vitest extension.
- Open the Test Results view.
- Observe that Vitest adds
Copy Error / Copy Test Errors to foreign result/message items.
Output
No Vitest Output channel was created in this reproduction.
The issue reproduces in a new no-workspace window before any Vitest project/runtime is active.
Extension Version
1.50.1
Vitest Version
N/A (no workspace/project/test files/any files in repro)
Validations
Describe the bug
Copy Error/Copy Test Errorsactions appear on non-Vitest test results.Clicking them on another controller's results is a no-op or can show unrelated Vitest warnings.
Vitest-specific copy actions seem to leak into foreign Testing controllers/results.
Expected behavior
Those actions should only appear for Vitest-owned results/messages.
Likely fix: add proper
whenscoping to the result/message menu contributions.Reproduction
Copy Error/Copy Test Errorsto foreign result/message items.Output
No Vitest Output channel was created in this reproduction.
The issue reproduces in a new no-workspace window before any Vitest project/runtime is active.
Extension Version
1.50.1
Vitest Version
N/A (no workspace/project/test files/any files in repro)
Validations