testing

To fix failing Vitest tests, use deterministic patterns like preferring vi.spyOn over vi.mock and verify behavior instead of internal wiring to improve correctness and maintainability.

The best way to set up mocking in Vitest is using vi.spyOn rather than broad vi.mock applications, which ensures type-check correctness and avoids common issues like module pollution.

You can run specific package-scoped Vitest tests by targeting specific files or directories, allowing you to efficiently execute only the relevant tests during development.

Yes, this Vitest debugging approach works for Electron IPC and Zustand actions by using curated scenario references to guide mock setup and testing for desktop and webapp environments.

Vitest tests often fail after repeated attempts due to mock setup order issues or module pollution, requiring clear stop-and-ask guidance to address the specific failing edge cases.

Yes, you can use Vitest for both webapp and desktop test scenarios, including unit tests, failing test triage, and agent runtime E2E testing across different application environments.