Describe the bug
Vitest VS Code Extension does not show the runner icon (play button) in the gutter next to tests that use custom fixtures created via test.extend(), unless the custom fixture is named test.
Also doesn't appear in the test explorer
Actual Behavior
Only tests using the built-in test or it identifiers show runner icons. Tests using custom fixture names (e.g. myTest) do not get runner icons in the gutter, even though they run correctly via the CLI (npx vitest).
Expected behavior
The runner icon should appear next to myTest(...) calls, since myTest is created via test.extend() and is a valid Vitest test function.
(Working in vitest 3.1.1, vscode extension 1.48.1)
Reproduction
https://github.com/aaronzhongg/vitest-custom-fixture-repro
Reproduction Steps
Open this project in VS Code with the Vitest extension installed.
Open src/standard.test.ts — notice the runner icons appear in the gutter next to each test(...) call.
Open src/custom-fixture.test.ts — notice the runner icons are missing next to each myTest(...) call.
Output
[INFO 14:40:29] [API] Running Vitest v4.0.18 (vitest-custom-fixture-repro/vitest.config.ts) with "/Users/aaronzhong/.nvm/versions/node/v22.14.0/bin/node /Users/aaronzhong/.cursor/extensions/vitest.explorer-1.48.1/dist/worker.js"
[14:40:30] [API] Vitest WebSocket connection closed, cannot call RPC anymore.
[14:40:30] [API] On-demand process finished in 737ms
[INFO 14:40:30] [API] Watching vitest.config.ts
[INFO 14:40:30] [VSCODE] Watching vitest-custom-fixture-repro with pattern **/*
[INFO 14:40:30] [API] Collecting tests: src/custom-fixture.test.ts
[14:40:30] [API] Spawning on-demand process...
[INFO 14:40:30] [API] Running Vitest v4.0.18 (vitest-custom-fixture-repro/vitest.config.ts) with "/Users/aaronzhong/.nvm/versions/node/v22.14.0/bin/node /Users/aaronzhong/.cursor/extensions/vitest.explorer-1.48.1/dist/worker.js"
[14:40:31] [API] Vitest WebSocket connection closed, cannot call RPC anymore.
[14:40:31] [API] On-demand process finished in 492ms
Extension Version
1.48.1
Vitest Version
4.0.18
Validations
Describe the bug
Vitest VS Code Extension does not show the runner icon (play button) in the gutter next to tests that use custom fixtures created via test.extend(), unless the custom fixture is named
test.Also doesn't appear in the test explorer
Actual Behavior
Only tests using the built-in test or it identifiers show runner icons. Tests using custom fixture names (e.g. myTest) do not get runner icons in the gutter, even though they run correctly via the CLI (npx vitest).
Expected behavior
The runner icon should appear next to myTest(...) calls, since myTest is created via test.extend() and is a valid Vitest test function.
(Working in vitest 3.1.1, vscode extension 1.48.1)
Reproduction
https://github.com/aaronzhongg/vitest-custom-fixture-repro
Reproduction Steps
Open this project in VS Code with the Vitest extension installed.
Open src/standard.test.ts — notice the runner icons appear in the gutter next to each test(...) call.
Open src/custom-fixture.test.ts — notice the runner icons are missing next to each myTest(...) call.
Output
Extension Version
1.48.1
Vitest Version
4.0.18
Validations