What problem does it solve?
It reduces flaky and hard-to-debug test failures by providing clear Vitest conventions for running, structuring, mocking, and iteratively fixing tests without overfitting to implementation details.
Core Features & Use Cases
- Targeted test execution: Run single files or package-specific tests to speed up feedback loops.
- Safer mocking strategy: Prefer
vi.spyOn and controlled browser/global stubs rather than broad module mocks.
- Failure triage workflow: Decide whether to update assertions (behavior changes) or stop and escalate after repeated unsuccessful fixes.
- Security-aware expectations: Reinforce that tests should verify externally observable behavior, not internal wiring.
- Practical references: Use deeper scenario docs for database model testing, Electron IPC, Zustand store actions, agent runtime E2E, and desktop controller units.
Quick Start
Run the specific failing test file with vitest using bunx and then adjust only behavior-focused expectations until the test passes.