STAGE 05 / CHAPTERS 17-18
Test quality and risk
Test the whole outcome, its boundaries, and its failure paths. Check the saved state as well as the message.
THE WORK TO DO
- 01
Exercise ordinary paths, overlaps, exact boundaries, delayed and repeated events, and lost responses.
- 02
Check permitted and forbidden actions on the server. Observe usability, accessibility, and behavior under the intended workload.
- 03
Reproduce defects, correct them, and repeat the failed and neighboring checks on the new version.
WHAT YOU LEAVE WITH
Versioned results, explained defects, and remaining risks with owners and workable restrictions.
BEFORE MOVING FORWARD
Critical behavior has evidence for the intended next use; any remaining restriction can actually be maintained.
A reschedule appears successful, but the old provider interval stays occupied. Looking at saved state exposes the defect that the success message misses.
WHO DOES WHAT / STAGE 05
Test the promises and the costly failures.
Tester
Runs the agreed checks and records scope and results.
Security Engineer
Tests forbidden and permitted operations directly.
Backend Developer
Corrects server and data failures.
Frontend Developer
Corrects interface behavior and status messages.
DevOps Engineer
Rehearses response and recovery.
THE HANDOFF
Test evidence + open issues → acceptance discussion
Findings return to the owner of the rule, design, implementation, or operating procedure. The Tester repeats affected checks on the corrected candidate.
Work with: Tech Lead, Analyst, Designer, Senior Administrator.
Additional expertise when the work needs it: Test Automation Engineer, Data and Database Specialist, Site Reliability Engineer.
See the team across all eight stages →