We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jest has JEST_WORKER_ID, which is useful for example when running X parallel tests, each test can connect to a different DB.
it would be nice to be able to use VITEST_WORKER_ID env var to identify workers. Ideally this would be a positive integer rather then a UUID
the worker ID could also be available as an export that clients could import for example like:
import { workerId } from 'vitest'
No response
The text was updated successfully, but these errors were encountered:
this will be released in 0.3.7 right?
Sorry, something went wrong.
Yes
Successfully merging a pull request may close this issue.
Clear and concise description of the problem
jest has JEST_WORKER_ID, which is useful for example when running X parallel tests, each test can connect to a different DB.
Suggested solution
it would be nice to be able to use VITEST_WORKER_ID env var to identify workers.
Ideally this would be a positive integer rather then a UUID
Alternative
the worker ID could also be available as an export that clients could import for example like:
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: