Can't run globalSetup with teardown without resetting extension

[MakoriSM]

Describe the bug

I'm using vitest for express testing but the extension is unusable for my use case. I want to:

1. Spin up a container to be used by all tests once
2. Pass the container URL in env variables so tests can reference it
3. Run my tests (with the env variables defined here)
4. Teardown my test containers

At present this isn't really possible with all of these approaches:

• globalSetup: This only runs once and then never again until you manually reload your tests (subsequent tests will not have proper setup). This can be circumvented with the onTestsRerun hook but then the teardown script will only run when reload is selected. This also runs in a separate context so environment variables need to be manually injected into test context with the project.provide function, adding a lot of overhead.
• custom reporters: This seemed promising but apparently reporters just don't run at all for some reason on the extension so this won’t work. Tried using onTestRunStart and onFinished hooks to perform setup and teardown respectively but this simply doesn't run at all when running tests by the extension

Currently it seems there’s no way to simply run a single global setup before all tests are ran so currently I’m just running via CLI until this can be resolved. Hopefully either by fixing reporters or by creating a pretest of some kind in the config.

Reproduction

https://github.com/MakoriSM/vitest-test

Output

This is my output whenever I run the onTestRerun hook setup version. Everything spins up (twice, once for each test environment I'd prefer only having 1 for all environments) but doesn't teardown. It includes extra console logs I've added:

[INFO 7:30:34 PM] Running 1 file(s): tests
[7:30:34 PM] Starting a test run because tests/unit/auth.service.test.ts tests/integration/basic.int.test.ts tests/integration/auth/basic.auth.int.test.ts triggered a watch rerun event
[7:30:34 PM] Enqueuing "noop test to preserve suite after Firebase migration"
[7:30:34 PM] Enqueuing "sets DATABASE_URL for per-file db"
[7:30:34 PM] Enqueuing "requires auth"
[7:30:34 PM] Enqueuing "accepts emulator token"
[7:30:34 PM] Enqueuing "noop test to preserve suite after Firebase migration"
[7:30:34 PM] Enqueuing "sets DATABASE_URL for per-file db"
[7:30:34 PM] Enqueuing "requires auth"
[7:30:34 PM] Enqueuing "accepts emulator token"
[7:30:34 PM] Enqueuing "noop test to preserve suite after Firebase migration"
[7:30:34 PM] Enqueuing "sets DATABASE_URL for per-file db"
[7:30:34 PM] Enqueuing "requires auth"
[7:30:34 PM] Enqueuing "accepts emulator token"
[INFO 7:30:34 PM] [Worker] globalSetup.ts: shouldSetupDb true
[INFO 7:30:36 PM] [Worker] globalSetup.ts: databaseUrl postgresql://postgres:password@localhost:32780/vitest_test
globalSetup.ts: toUrlWithDb postgresql://postgres:password@localhost:32780/vitest_test postgres
globalSetup.ts: toUrlWithDb postgresql://postgres:password@localhost:32780/vitest_test vitest_template
[INFO 7:30:38 PM] [Worker] 
[INFO 7:30:39 PM] [Worker] Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "vitest_test", schema "public" at "localhost:32780"
[INFO 7:30:39 PM] [Worker] 
🚀  Your database is now in sync with your Prisma schema. Done in 98ms

⠙
[INFO 7:30:42 PM] [Worker] globalSetup.ts: endpoint http://localhost:32781
[INFO 7:30:54 PM] [Worker] globalSetup.ts: shouldSetupDb true
[INFO 7:30:56 PM] [Worker] globalSetup.ts: databaseUrl postgresql://postgres:password@localhost:32783/vitest_test
globalSetup.ts: toUrlWithDb postgresql://postgres:password@localhost:32783/vitest_test postgres
globalSetup.ts: toUrlWithDb postgresql://postgres:password@localhost:32783/vitest_test vitest_template
[INFO 7:30:58 PM] [Worker] 
[INFO 7:30:59 PM] [Worker] Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "vitest_test", schema "public" at "localhost:32783"
[INFO 7:30:59 PM] [Worker] 
🚀  Your database is now in sync with your Prisma schema. Done in 148ms

⠙
[INFO 7:31:02 PM] [Worker] globalSetup.ts: endpoint http://localhost:32784
[7:31:15 PM] No task result for "auth.service.test.ts [unit]", ignoring
[7:31:15 PM] No task result for "AuthService", ignoring
[7:31:15 PM] Enqueuing "noop test to preserve suite after Firebase migration" because it was just collected
[7:31:15 PM] No errors found for "auth.service.test.ts [unit]"
[7:31:15 PM] No errors found for "AuthService"
[7:31:15 PM] Marking "noop test to preserve suite after Firebase migration" as passed
[7:31:15 PM] No errors found for "auth.service.test.ts [unit]"
[7:31:15 PM] No task result for "basic.int.test.ts [int]", ignoring
[7:31:15 PM] No task result for "basic infra smoke", ignoring
[7:31:15 PM] Enqueuing "sets DATABASE_URL for per-file db" because it was just collected
[7:31:15 PM] No errors found for "basic.int.test.ts [int]"
[7:31:15 PM] No errors found for "basic.int.test.ts [int]"
[7:31:15 PM] No errors found for "basic infra smoke"
[7:31:15 PM] Marking "sets DATABASE_URL for per-file db" as passed
[7:31:15 PM] No errors found for "basic.int.test.ts [int]"
[7:31:15 PM] No task result for "basic.auth.int.test.ts [int-auth]", ignoring
[7:31:15 PM] Enqueuing "requires auth" because it was just collected
[7:31:15 PM] Enqueuing "accepts emulator token" because it was just collected
[7:31:15 PM] No errors found for "basic.auth.int.test.ts [int-auth]"
[7:31:15 PM] No errors found for "basic.auth.int.test.ts [int-auth]"
[7:31:16 PM] Marking "requires auth" as passed
[7:31:16 PM] Marking "accepts emulator token" as passed
[7:31:16 PM] No errors found for "basic.auth.int.test.ts [int-auth]"
[7:31:16 PM] Ending test run 
[7:31:16 PM] Test run promise is finished, the queue is 0
[7:31:16 PM] [VSCODE] Ignoring file: node_modules/.vite/vitest/da39a3ee5e6b4b0d3255bfef95601890afd80709/results.json

Extension Version

1.32.0

Vitest Version

3.2.4

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.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[keithyipkw]

Coincidentally, I ran into the same issue with a similar usage. The global setup and teardown behaviours between run once and debug are inconsistent and messy. I am not sure if they are intended.

When debugging tests, the global setup is performed first, and the teardown is performed after the tests finish as expected. However, the teardown function is not called when running tests once. Only when refreshing the tests or closing VS Code, the teardown function is called. The continuous run mode behaves the same, but arguably, it is right.

The global setup and teardown are also problematic when debugging tests after running tests once. The teardown corresponding to the running once is not called before the global setup of the debugging is performed. As a result, two consecutive global setups are performed.

It is also quite inconvenient when modifying and re-running the global setup script using the extension.

I have added a test sample to my fork of this repo, the global-setup branch in https://github.com/keithyipkw/vitest-vscode

Reproduction

1. Clone the global-setup branch in https://github.com/keithyipkw/vitest-vscode
2. pnpm i && pnpm dev
3. Run and Debug: Run Extension Global Setup
4. In the new VS Code instance, run the test "run"
5. Debug the same test
6. Click "Refresh Tests"

Output

Output highlight

[INFO 12:48:41 PM] [Worker] Global setup 8fbbd19
[INFO 12:48:41 PM] [Worker] Global setup 8fbbd19
[INFO 12:48:49 PM] [Worker] Global setup c19e2d9
[INFO 12:48:50 PM] [Worker] Global teardown c19e2d9
[INFO 12:48:54 PM] [Worker] Global teardown 8fbbd19
[INFO 12:48:54 PM] [Worker] Global teardown 8fbbd19

Custom log file

Global setup 8fbbd191
Global setup c19e2d95
Global teardown c19e2d95
Global teardown 8fbbd191

Full output

[INFO 12:48:26 PM] [v0.0.0] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 12:48:26 PM] [API] Resolving configs: global-setup/vitest.config.ts
[INFO 12:48:27 PM] [API] Running Vitest v4.0.0-beta.12 (global-setup/vitest.config.ts) with "C:\nvm4w\nodejs\node.EXE C:/Users/user/Workspace/vitest-vscode/dist/worker.js"
[INFO 12:48:27 PM] [API] Watching vitest.config.ts
[INFO 12:48:27 PM] [VSCODE] Watching global-setup with pattern **/*
[INFO 12:48:30 PM] [API] Collecting tests: test/run.test.ts
[INFO 12:48:41 PM] Running 1 file(s) with name pattern: ^\s?testing run$
[12:48:41 PM] Starting a test run because test/run.test.ts triggered a watch rerun event
[12:48:41 PM] Enqueuing "run"
[INFO 12:48:41 PM] [Worker] Global setup 8fbbd19
[INFO 12:48:41 PM] [Worker] Global setup 8fbbd19
[12:48:41 PM] [VSCODE] File changed: log
[12:48:41 PM] No task result for "run.test.ts", ignoring
[12:48:41 PM] No task result for "testing", ignoring
[12:48:41 PM] Enqueuing "run" because it was just collected
[12:48:41 PM] No errors found for "run.test.ts"
[12:48:41 PM] No errors found for "testing"
[12:48:41 PM] Marking "run" as passed
[12:48:41 PM] No errors found for "run.test.ts"
[12:48:41 PM] Ending test run test/run.test.ts
[12:48:41 PM] Test run promise is finished, the queue is 0
[12:48:41 PM] [VSCODE] Ignoring file: node_modules\.vite\vitest\da39a3ee5e6b4b0d3255bfef95601890afd80709\results.json
[INFO 12:48:48 PM] [DEBUG] Starting debugging session C:\nvm4w\nodejs\node.EXE
[INFO 12:48:48 PM] [DEBUG] Debugging started
[INFO 12:48:49 PM] Running 1 file(s) with name pattern: ^\s?testing run$
[12:48:49 PM] Starting a test run because test/run.test.ts triggered a watch rerun event
[12:48:49 PM] Enqueuing "run"
[INFO 12:48:49 PM] [Worker] Global setup c19e2d9
[12:48:49 PM] [VSCODE] File changed: log
[12:48:50 PM] No task result for "run.test.ts", ignoring
[12:48:50 PM] No task result for "testing", ignoring
[12:48:50 PM] Enqueuing "run" because it was just collected
[12:48:50 PM] No errors found for "run.test.ts"
[12:48:50 PM] No errors found for "testing"
[12:48:50 PM] Marking "run" as passed
[12:48:50 PM] No errors found for "run.test.ts"
[INFO 12:48:50 PM] [Worker] Global teardown c19e2d9
[12:48:50 PM] Ending test run test/run.test.ts
[12:48:50 PM] Test run promise is finished, the queue is 0
[12:48:50 PM] [VSCODE] Ignoring file: node_modules\.vite\vitest\da39a3ee5e6b4b0d3255bfef95601890afd80709\results.json
[12:48:50 PM] [VSCODE] File changed: log
[12:48:50 PM] [API] Vitest WebSocket connection closed, cannot call RPC anymore.
[12:48:50 PM] Ending test run <none>
[12:48:50 PM] Disposing test runner
[12:48:50 PM] Ending test run <none>
[12:48:54 PM] Disposing test runner
[12:48:54 PM] Ending test run <none>
[INFO 12:48:54 PM] [Worker] Global teardown 8fbbd19
[INFO 12:48:54 PM] [Worker] Global teardown 8fbbd19
[INFO 12:48:54 PM] [API] Vitest process 25524 closed successfully
[12:48:54 PM] [API] Vitest WebSocket connection closed, cannot call RPC anymore.
[Error 12:48:54 PM] Failed to close server
[INFO 12:48:54 PM] [API] Resolving configs: global-setup/vitest.config.ts
[INFO 12:48:54 PM] [API] Running Vitest v4.0.0-beta.12 (global-setup/vitest.config.ts) with "C:\nvm4w\nodejs\node.EXE C:/Users/user/Workspace/vitest-vscode/dist/worker.js"
[INFO 12:48:54 PM] [API] Watching vitest.config.ts
[INFO 12:48:54 PM] [VSCODE] Watching global-setup with pattern **/*
[INFO 12:48:55 PM] [API] Collecting tests: test/run.test.ts

Extension Version

Commit 77d7e17 (the current main)

Vitest Version

4.0.0-beta.12