manual-testing

# Manual Testing

Verify current work through automated testing first, falling back to user verification only when necessary.

## Core Principle

**Automate everything possible.** Only ask the user to manually verify what Claude cannot verify through tools.

## Workflow

### 1. Analyze Current Context

Examine recent work to identify what needs testing:
- Review recent file changes and conversation history
- Identify the feature, fix, or change to verify
- Determine testable behaviors and expected outcomes

### 2. Classify Each Verification Step

For each thing to verify, determine if Claude can test it automatically:

**Claude CAN verify (do these automatically):**
- Code compiles/builds: `npm run build`, `cargo build`, `go build`, etc.
- Tests pass: `npm test`, `pytest`, `cargo test`, etc.
- Linting/type checking: `eslint`, `tsc --noEmit`, `mypy`, etc.
- API responses: `curl`, `httpie`, or scripted requests
- File contents: Read files, grep for expected patterns
- CLI tool output: Run commands and check output
- Server starts: Start server, check for errors, verify endpoints respond
- Database state: Query databases, check records exist
- Log output: Tail logs, grep for expected/unexpected messages
- Process behavior: Check exit codes, stdout/stderr content
- File existence/permissions: `ls`, `stat`, `test -f`
- JSON/config validity: Parse and validate structure
- Port availability: `lsof`, `netstat`, curl localhost
- Git state: Check diffs, commits, branch state

**Claude CANNOT verify (ask user):**
- Visual appearance (colors, layout, spacing, alignment)
- Animations and transitions
- User experience feel (responsiveness, intuition)
- Cross-browser rendering
- Mobile device behavior
- Physical hardware interaction
- Third-party service UIs (OAuth flows, payment forms)
- Accessibility with actual screen readers
- Performance perception (feels fast/slow)

### 3. Execute Automated Verifications

Run all automatable checks first. Be thorough:

```bash
# Example: Tes