Testing

Given task file path .plans/<project>/testing/NNN-task.md:

Process

Use TodoWrite to track testing validation:

☐ Validate existing tests (behavior-focused?)
☐ Check coverage of Validation checklist items
☐ Identify gaps (empty/null, boundaries, errors)
☐ Add tests for genuine gaps
☐ Run coverage (>80% statements, >75% branches)
☐ Update task status

1. Validate existing tests - behavior-focused? Covers Validation?
2. Identify gaps - empty/null inputs, boundaries, errors, race conditions, security
3. Add minimal tests if genuinely missing
4. Run coverage - verify >80% statements, >75% branches
5. Update task status using Edit tool:
   • Find: **Status:** [current status]
   • Replace: **Status:** READY_FOR_REVIEW
6. Append testing notes using Edit tool (add to end of task file):

   **testing:**
   Validated [N] tests (behavior-focused)
   
   Added [M] edge cases:
   - [Test description]
   - [Test description]
   
   Test breakdown: Unit: X | Integration: Y | Total: Z
   Coverage: Statements: XX% | Branches: XX% | Functions: XX% | Lines: XX%
   Full suite: XXX/XXX passing
   Working Result verified: ✓ [description]
   

7. Report completion

Test Quality

Good: expect(response.status).toBe(401) (tests behavior) Bad: expect(bcrypt.compare).toHaveBeenCalled() (tests implementation)

Granularity: Pure functions → Unit | DB/API → Integration | Critical workflows → E2E (rare)

Failure Handling

If tests fail or coverage <80%:

• Fix test scenarios first
• If code bug found:
  • Update status using Edit tool: Find **Status:** [current status] → Replace **Status:** NEEDS_FIX
  • Append notes using Edit tool (append to end of file):

    **testing:**
    Found issues:
    - [Specific issue]
    - [Specific issue]
    
    Requires code fixes. Moving back to implementation.
    

Completion

When testing is complete (status updated to READY_FOR_REVIEW or NEEDS_FIX):

• Report: ✅ Testing complete. Status: [STATUS]