Skip to content
New issue

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

slowTestThreshold doesn't seem to be working #4869

Closed
6 tasks done
iby opened this issue Jan 4, 2024 · 1 comment · Fixed by #4876
Closed
6 tasks done

slowTestThreshold doesn't seem to be working #4869

iby opened this issue Jan 4, 2024 · 1 comment · Fixed by #4876
Labels
p3-minor-bug An edge case that only affects very specific usage (priority) pr welcome

Comments

@iby
Copy link

iby commented Jan 4, 2024

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:

image

System Info

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

Used Package Manager

npm

Validations

@iby
Copy link
Author

iby commented Jan 6, 2024

@sheremet-va thank you! 🙏

@github-actions github-actions bot locked and limited conversation to collaborators Jan 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug An edge case that only affects very specific usage (priority) pr welcome
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants