testing

Risk-based test strategy with perspective tables, structured case design, and coverage evidence.

Workflow

1. Classify risk — low, medium, or high based on blast radius and failure cost.
2. Build perspective table — define case IDs and expected behavior before writing tests (required for medium/high risk; recommended for low).
3. Choose test mix — unit for logic branches, integration for boundary contracts, E2E when user flow risk is high.
4. Design cases — equivalence classes, boundary values, failure-mode checks.
5. Implement and run — execute relevant suites, collect coverage evidence.
6. Report — summarize protected behavior, known gaps, commands run, coverage data.

Test Perspective Table