test

Test

When to use

• Files, or changed code, have gaps in coverage

Goal

• Write comprehensive and exhaustive tests that address gaps in code coverage.

Input

Determine scope from the first available source:

• Files or folders provided by the user.
• Current changes in the repository.

Abort if no scope exists.

Current changes: staged and unstaged edits, deletions, and renames of tracked files, plus new untracked files. Requires a versioned project. Abort with a clear message if none detected.

Testing

See references/testing-guide.md for test structure, isolation, mocking, assertion, and performance standards.

Shell commands

See references/shell-command-guide.md for command safety, timeouts, redirects, and non-interactive environment directives.

Cleanup

See references/cleanup-guide.md for the self-introduced-artifact checklist and diff-only audit scope.

Behavioral surface

Target only methods and functions with business logic, state transitions, or error handling. Exclude: trivial getters/setters, POJOs, generated code, framework boilerplate, and any method where every path delegates trivially, accesses a field, or returns a computed value with no state change, resource interaction, or error-propagation decision.

Workflow

1. GATE—Confirm scope: user-provided files or current repository changes. Abort immediately if none.
2. ORIENT—Goal: cover all behavioral gaps in scope. Production code unchanged.
3. PLAN—Read references/testing-guide.md, references/shell-command-guide.md, and references/cleanup-guide.md. Inspect production code, adjacent tests, and coverage commands. List every gap across all four categories per behavioral-surface target.
   • Short-circuit: zero gaps found → emit Result: No Gaps and halt.
4. ACT—Write tests for every enumerated gap. Cover all four categories per target before declaring it complete.
5. VERIFY—Loop over every criterion declared in PLAN:
   • Run targeted tests; run broader suite or coverage tool.
   • Audit every new test file against CI Parity rules in references/testing-guide.md; fix any violation before proceeding.
   • Audit the task's own git diff/git status against the Self-cleanup checklist in references/cleanup-guide.md; remove every self-introduced artifact before proceeding.
   • For each unmet criterion: return to ACT, execute, then re-enter VERIFY.
   • Exit only when all pass and no regressions remain.
   • Halt only for out-of-scope blockers.
6. PERSIST—Confirm all test files written; no partial writes.
7. REPORT—Emit the result following the result directives and using the result template.