testing

The best way to structure Vitest tests involves following a structured guide that enforces best practices for organizing tests across Webapp, Packages, and Desktop codebases. This approach improves test reliability and coverage by referencing dedicated guidance in references/.

To use vi.spyOn instead of broad vi.mock, apply the Skill's mocking strategies that enforce best practices for spying on dependencies. This targeted approach avoids the pitfalls of broad mocking and ensures reliable test behavior across your codebases.

To run targeted Vitest tests for a specific file, execute the command `bunx vitest run --silent='passed-only' '[path-to-test]'`. This allows you to isolate and debug specific test scenarios efficiently during maintenance workflows.

Yes, this Vitest guidance covers strategies for failing tests and test maintenance across Webapp, Packages, and Desktop codebases. It provides real-world examples and patterns to improve test reliability and coverage while debugging.

You should avoid broad vi.mock because it can introduce errors and reduce test reliability. The Skill enforces best practices by using vi.spyOn for mocking dependencies, providing a more targeted and reliable testing pattern for your codebase.