Testing and quality foundations

Review questions

Subject synthesis: Testing and quality foundations

Quality testing separates the requested rule, observed result, and remaining assumption. Three delivered messages establish delivery only for those attempts; they do not prove correct storage or usefulness to every user. Identify the quality attribute, environment, inputs, expected outcome and observation before making a claim. An ambiguous rule, such as a missing time-zone label, needs a clarified meaning. Test levels locate where evidence can be collected without naming an unproved root cause. Static review can expose a contradictory rule before code runs, while execution shows behaviour. Verification asks whether the implementation follows a specification; validation asks whether the service meets a user need. The subject closes with an evidence record that names passed, failed and unperformed cases and proposes the next check for each consequential gap.

Review questions

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

  1. Question 1If messages arrived for two bookings, what is the narrowest supported claim?
  2. Question 2A success screen appears but the database stores another date. What evidence matters?
  3. Question 3A date function passes alone but confirmation fails. Where should fault localization begin?
  4. Question 4A rule says “send the reminder early” without a time. What is the best preparation?