04 / Test approach
From requirements to useful evidence.
My proposed process for identifying risk, designing coverage, and communicating what a release still needs.
01 — Understand the product
Identify users, goals, and the cost of failure. Clarify acceptance criteria and ambiguous rules before treating them as test expectations.
02 — Design coverage
Map the normal journey, then vary roles, inputs, states, and dependencies. Prioritize private data, transaction integrity, and blocked user journeys.
- Record preconditions and representative data
- Use boundary values and invalid input classes
- Include interrupted requests and repeated actions
03 — Execute & investigate
Compare observations with agreed expectations. Inspect interface behavior, API responses, and persisted records where access permits. Record the environment and build with the evidence.
04 — Report & retest
Explain impact with minimal reproduction steps. After a fix, repeat the failing case and nearby scenarios. Document untested areas and remaining risks before a release decision.