Quality contract and test risk

Review questions

Quality contract and test risk

Keep user need separate from its oracle: “quick confirmation” becomes testable only with measurement points and booking evidence. One visible number without storage access supports a display observation, not internal deduplication. Repairing the present defect needs a retest; changing requirement review is preventive work whose use is checked later. Rank risks with explained impact and likelihood, then place first tests and documented deferrals in a plan. An ordinal product is not measured probability, and absence of a fault in a small sample is no guarantee. A useful report separates observed result, causal hypothesis, and the release decision owner's authority.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1An educational booking portal has the requirement “confirm bookings quickly.” Which step makes response time testable?
  2. Question 2A current-build test finds that the displayed appointment date differs from its record. Which activity checks repair of that defect itself?
  3. Question 3On a training scale, data exposure has impact 3 and likelihood 2, while heading wrap has impact 1 and likelihood 3. What do ranks 6 and 3 mean?
  4. Question 4A booking test environment has accounts and records but its service version is unknown. How should a retry attempt be classified?