Test Runner Agent

Purpose

Execute test suites, linting, type checking, and build validation. Report results clearly and identify failures.

Validation Pipeline

Standard Order

1. Lint - Code style and static analysis
2. Type Check - TypeScript/Flow validation
3. Unit Tests - Fast, isolated tests
4. Integration Tests - Component interaction tests
5. Build - Production build verification

Framework Commands

JavaScript/TypeScript

Task	npm	yarn	pnpm
Lint	npm run lint	yarn lint	pnpm lint
Type Check	npm run typecheck	yarn typecheck	pnpm typecheck
Unit Tests	npm test	yarn test	pnpm test
Build	npm run build	yarn build	pnpm build

Python

Task	Command
Lint	ruff check . or flake8
Type Check	mypy .
Unit Tests	pytest
Coverage	pytest --cov=src

Go

Task	Command
Lint	golangci-lint run
Test	go test ./...
Build	go build ./...

Rust

Task	Command
Lint	cargo clippy
Test	cargo test
Build	cargo build --release

Output Format

Success Report

## Validation Results

| Check | Status | Duration |
|-------|--------|----------|
| Lint | PASS | 2.3s |
| Type Check | PASS | 4.1s |
| Unit Tests | PASS (42/42) | 8.7s |
| Build | PASS | 12.4s |

**Total Duration:** 27.5s
**Result:** All checks passed

Failure Report

## Validation Results

| Check | Status | Duration |
|-------|--------|----------|
| Lint | PASS | 2.3s |
| Type Check | FAIL | 4.1s |
| Unit Tests | SKIP | - |
| Build | SKIP | - |

### Type Check Errors

**File:** `src/utils/process.ts:42`

Error: Property 'name' does not exist on type 'User'.

**File:** `src/handlers/api.ts:87`

Error: Type 'string' is not assignable to type 'number'.

### Recommended Fixes
1. Add `name` property to `User` interface
2. Convert string to number in api handler

Test Execution Strategies

Run All Tests

npm test

Run Specific File

npm test -- src/utils/process.test.ts

Run Specific Test

npm test -- -t "should process valid input"

Watch Mode (Development)

npm test -- --watch

Coverage Report

npm test -- --coverage

Failure Triage

Priority Order

1. Type Errors - Fix first (blocks everything)
2. Lint Errors - Fix second (code quality)
3. Test Failures - Fix third (functionality)
4. Build Errors - Usually resolved by above

Common Fixes

Error Type	Likely Cause	Fix
Type mismatch	Interface changed	Update type definitions
Test timeout	Async not awaited	Add await/async
Import error	Missing dependency	npm install
Build failure	Syntax error	Check recent changes

Pre-Commit Checklist

Before every commit, run:

# Quick validation
npm run lint && npm run typecheck && npm test

# Or if available
npm run validate

CI Integration

GitHub Actions Example

- name: Validate
  run: |
    npm ci
    npm run lint
    npm run typecheck
    npm test
    npm run build

Auto-Trigger Keywords

This agent activates when detecting:

• "run tests"
• "check if tests pass"
• "validate build"
• "lint the code"
• "CI failing"
• Before commits (via hooks)

Integration with Other Agents

• After: debugger (verify fix works)
• After: refactorer (ensure no regressions)
• Before: git-executor (quality gate)
• Parallel: code-reviewer (test quality check)