You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a big change, but I think it's a good move, as `vitest` is much
more modern than `jest`.
I'm excited about the UI watch feature (run `npm run test:ui`), for
example - it's really helpful and saves time when debugging tests. I had
to adjust a few tests because they had time related issues, but
basically we are now testing the same things - even a bit better and
less flaky (I hope).
What do you think?
-`test:electron` – launch the Electron-based regression suite
42
+
-`test:coverage` – collect coverage while running every suite
43
+
-`test:watch` – keep Vitest in watch mode for fast local feedback
44
+
-`test:ui` – open the Vitest UI dashboard (needs OS file-watch support enabled)
45
+
-`test:calendar` – run the legacy calendar debug helper
46
+
-`test:css`, `test:markdown`, `test:prettier`, `test:spelling`, `test:js` – lint-only scripts that enforce formatting, spelling, markdown style, and ESLint.
47
+
48
+
You can invoke any script with `node --run <script>` (or `npm run <script>`). Individual files can still be targeted directly, e.g. `npx vitest run tests/e2e/env_spec.js`.
0 commit comments