Run Tests

Execute the project's test suite, analyze failures, attempt fixes, and re-run. Designed as a reusable sub-workflow called by /feature-dev, /bugfix, and /pre-commit.

Uses testing-procedures skill for test writing patterns and coverage targets.

1. Detect Test Stack

Read TESTING.md (if exists) for test commands, infrastructure, and credentials. Fall back to CLAUDE.md and project config to determine:

2. Run Tests

Execute the test suite:

// turbo
<test-command>

Capture:

• Exit code: 0 = all pass, non-zero = failures
• Output: Test names, pass/fail counts, error messages, stack traces

3. Analyze Failures

If tests fail, for each failure:

1. Read the failing test — understand what it asserts
2. Read the error message and stack trace — identify the actual vs expected
3. Classify the failure:

4. Fix and Re-Run

For auto-fixable failures:

1. Apply the appropriate stack-specific role (Agent(frontend-engineer), Agent(java-engineer), Agent(python-engineer), etc.)
2. Apply the minimal fix — do not refactor unrelated code
3. Re-run the failing test(s) specifically:

4. If the fix works, re-run the full suite to check for regressions
5. Max 3 fix attempts per failure — if still failing after 3 tries, escalate to user

5. Coverage Check (if available)

Run coverage report:

Compare against testing-procedures skill targets:

• Line coverage ≥ 80% (hard minimum 60%)
• Branch coverage ≥ 75% (hard minimum 50%)
• New code coverage ≥ 90%

6. Summary

## Test Results

| Metric | Value |
|--------|-------|
| Total tests | X |
| Passed | X |
| Failed | X |
| Skipped | X |
| Duration | Xs |
| Coverage | X% (target: 80%) |

### Failures Fixed
- [test name] — [what was wrong] — [fix applied]

### Remaining Failures (needs attention)
- [test name] — [error] — [classification]

### Coverage Gaps
- [file/module] — [current%] — [uncovered lines]

**Overall**: ✅ PASS / ❌ FAIL — [action needed]

Integration

• Called by: /feature-dev, /bugfix, /pre-commit
• Skills: testing-procedures skill
• Roles: Agent(qa-engineer) (test strategy), stack-specific role (implementation)