enforce-rules-for-vitest

name	enforce-rules-for-vitest
description	Enforce AIRI's testing and Vitest practices. Use when creating, editing, reviewing, or debugging tests; reproducing a reported bug or issue; changing Vitest configuration; mocking IPC, services, providers, platform APIs, or imports; or diagnosing test import and runtime-boundary failures in the AIRI monorepo.

Enforce AIRI Vitest Rules

Apply these rules to every test change in AIRI.

Choose the Test Scope

• Use the Vitest project that owns the affected code and keep runs targeted for speed.
• Grow component and end-to-end coverage progressively. Prefer Vitest browser mode when the behavior depends on DOM or Web Platform APIs.
• Use the smallest automated test that faithfully exercises the behavior: prefer a unit test, then the smallest suitable higher-level test.

Reproduce Bugs Before Fixing Them

1. For an investigated bug or issue, try to add a test-only reproduction before changing production code.
2. When reproduction is possible, include the tracker identifier in the test case name:
   • Use Issue #<number> for a GitHub issue.
   • Use the Linear issue key for an internal Linear bug.
3. Put the actual report URL in a comment directly above the regression test. Use the GitHub issue URL, Discord message or thread URL, or Linear issue URL as appropriate.
4. Confirm that the reproduction fails for the reported reason before implementing the fix.

Mock Real Boundaries

• Mock Electron IPC and Electron services with vi.fn or vi.mock; never require a real Electron runtime.
• For external providers and services, add mock-based tests and, when feasible, integration-style tests guarded by environment variables, but do not mock Pinia, Vue components. Vitest import mocks are allowed for these boundaries.
• Assert observable behavior, including mock calls and parameters, with explicit statements.