Testing Rules

Use this file only for tasks that add, change, or diagnose tests.

Scope

• Add or update only tests directly affected by the requested change.
• Prefer one focused test over broad generated suites.
• Cover the changed behavior and the most likely regression path.
• Do not create frontend + backend + integration coverage unless the change crosses those boundaries.

Commands

• Discover existing test scripts before adding tooling.
• Run the most relevant test file first.
• Run a wider suite only when the change touches shared code, public APIs, persistence, auth, build config, or test infrastructure.
• Report exact commands run and any skipped checks.

Coverage

• Use existing coverage tooling when already configured.
• Do not chase arbitrary 90% coverage for small edits.
• Raise coverage only where the changed behavior is under-tested and the project already measures it.