Quality contract and test risk

Begin by converting a vague booking request into an acceptance condition with starting state, action, observable result, and an independent oracle. Learn why a confirmation on screen does not establish persistence and why an unresolved rule must remain a decision question. Distinguish discovery of a defect in a current build from a process change intended to prevent recurrence. Use impact and likelihood ratings to prioritize cases while keeping the ratings separate from measured probability. Then create a small test plan that traces risk to cases, environment, entry conditions, and exit reporting. The practical outputs are an acceptance table, QA and QC matrix, risk register, and plan that show the release owner what was checked and what remains uncertain.

Read the whole first subject without an account: its lessons, summary and review questions.