Tests are split by categories. Default categories are:
These tests are running in different pools with a single config file. If you just need to test a function call, you can place your test here.
This is the only test category that doesn't start new Vitest instance for every test.
If you are testing a complex interaction, place your tests here.
- Config options go to
test/e2e/test/config/. - Vitest behaviour when file is created/updated/removed goes to
test/e2e/test/watch/. - Type-focused fixtures live under
test/e2e/dts/.
If you are testing browser mode, add your tests here.
These are e2e tests for UI package. We are using playwright to test it.
All other categories just group tests by type.
Where each suite runs in ci.yml, which is the source of truth:
| platform | unit | e2e | coverage | browser |
|---|---|---|---|---|
| ubuntu · node 22 | ✅ | |||
| ubuntu · node 24 | ✅ | ✅ | ✅ | ✅ 2 shards (whole suite) |
| ubuntu · node 26 | ✅ | ✅ | ✅ | |
| windows · node 24 | ✅ | ✅ | ✅ | ✅ runner isolated + 2 shards (excl. runner) |
| macos · node 24 | ✅ | |||
| ubuntu · node 24 · vite 7 | ✅ | 🟡 runner only |
The unit column is pnpm test:ci:unit, which runs every test package other than e2e, coverage, and browser, including test/unit and test/ui.