-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
p2-nice-to-haveNot breaking anything but nice to have (priority)Not breaking anything but nice to have (priority)pr welcome
Description
Describe the bug
I want tests to run in random order, and I also want slower test suites to run first and quicker test suites to run last, but it seems impossible without implementing a custom sequencer.
With test suites/files being isolated, I don't see the point of also running the test suites/files in random order.
Reproduction
- run
npm run test:runto build the cache - try
npm run test:runmultiple times, you'll see the test suites run in random order - set
shuffletofalse, runnpm run test:run, notice thattest/slow.test.tsstarts first
System Info
System:
OS: Windows 10 10.0.22621
CPU: (64) x64 AMD Ryzen Threadripper 3970X 32-Core Processor
Memory: 17.54 GB / 31.86 GB
Binaries:
Node: 20.2.0 - C:\Program Files\nodejs\node.EXE
npm: 9.6.7 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22621.1778.0), Chromium (114.0.1823.43)
Internet Explorer: 11.0.22621.1
npmPackages:
@vitejs/plugin-react: ^4.0.0 => 4.0.0
@vitest/coverage-v8: ^0.32.0 => 0.32.0
vite: ^4.3.5 => 4.3.9
vitest: ^0.32.0 => 0.32.0Used Package Manager
npm
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- 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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
p2-nice-to-haveNot breaking anything but nice to have (priority)Not breaking anything but nice to have (priority)pr welcome