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
Firstly, thank you for the amazingly fantastically wonderful tool and ending my toxic relationship with Jest! ❤️
It appears that slowTestThreshold isn't being picked up, unless I'm missing something?
Related:
With slowTestThreshold: 1000 Vitest still appears to be using the default the default 300 ms value, see StackBlitz playground:
slowTestThreshold: 1000
System: OS: macOS 14.2.1 CPU: (14) arm64 Apple M3 Max Memory: 425.16 MB / 36.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.10.0 - ~/Library/Caches/fnm_multishells/19299_1703443938118/bin/node npm: 10.2.5 - ~/Library/Caches/fnm_multishells/19299_1703443938118/bin/npm pnpm: 8.14.0 - /opt/homebrew/bin/pnpm Browsers: Chrome: 120.0.6099.129 Safari: 17.2.1 npmPackages: vitest: ^1.1.1 => 1.1.1
npm
The text was updated successfully, but these errors were encountered:
slowTestThreshold
@sheremet-va thank you! 🙏
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Firstly, thank you for the amazingly fantastically wonderful tool and ending my toxic relationship with Jest! ❤️
Describe the bug
It appears that slowTestThreshold isn't being picked up, unless I'm missing something?
Related:
Reproduction
With
slowTestThreshold: 1000
Vitest still appears to be using the default the default 300 ms value, see StackBlitz playground:System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: