Steps 7-8: Test and Verify

What your agent does

Runs integration tests across the entire application, then validates every acceptance criterion from the PRD against the running app.

Why this matters

Building features is only half the job. The other half is proving they work. The acceptance checklist from Step 2 becomes the scorecard — every criterion gets checked off or flagged.

Integration verification

The agent starts the dev server and tests every API endpoint documented in the PRD:

POST /api/auth/signup     → 201 ✓
POST /api/auth/login      → 200 ✓
GET  /api/monitors        → 200 ✓
POST /api/monitors        → 201 ✓
GET  /api/monitors/:id    → 200 ✓
DELETE /api/monitors/:id  → 204 ✓
GET  /api/cron/ping       → 200 ✓

It also triggers background jobs, verifies data flows end-to-end, and checks edge cases (invalid input, auth required, not found).

Acceptance criteria check

The agent goes through docs/prd/acceptance-checklist.md line by line:

[x] AC-001.1: Valid URL → appears in monitor list ✓
[x] AC-001.2: Invalid URL → validation error ✓
[x] AC-001.3: First ping → status updates ✓
[ ] AC-004.2: 7-day chart view → DEFERRED (needs 7 days of data)

You get a pass rate: "18/20 acceptance criteria passing (90%). 2 deferred."

Your role

Review the results. The agent reports:

• Which ACs are passing

• Which are failing (with details)

• Which are deferred (and why)

Decide whether the pass rate is acceptable for your needs.

Next: Screenshots and documentation →