6.4The Review Workflow in Practice

1. RECEIVE AI output (20-40 tests, ~5 minutes of generation time)

2. PASS 1 — SCAN test names (2 minutes)
   - Delete tests with vague names
   - Flag duplicate scenarios
   - Count: typically discard 10-15% here

3. PASS 2 — CHECK assertions (5 minutes)
   - Verify expected values against the spec
   - Flag tautology tests (testing the mock, not the code)
   - Flag weak assertions (status-code-only)
   - Count: typically flag 15-25% for revision

4. PASS 3 — DEEP REVIEW (10 minutes)
   - Check independence (no shared state)
   - Check determinism (no time/random dependencies)
   - Check setup/teardown completeness
   - Verify all referenced APIs exist in the codebase
   - Count: typically catch 5-10% more issues

5. REVISE flagged tests (5-10 minutes)
   - Fix assertions
   - Add missing setup/teardown
   - Strengthen weak assertions
   - Delete beyond-repair tests

6. RUN the suite (2 minutes)
   - Fix import errors
   - Fix missing fixtures
   - Verify all tests pass

Total: ~30 minutes for a 30-test suite
Without AI: ~4-6 hours to write the same 30 tests from scratch