Question 1
At fictional Lakeside Hospitality, the quality team is reviewing a change to its guest check-in service. A team uses a heavyweight approval script for a one-day prototype and receives test feedback after the prototype is obsolete. Which recurring practice would most directly reduce the chance of this situation recurring?
Explanation
Correct Answer
The recurring safeguard is to tailor test documentation and review depth to change speed, risks and lifecycle context. The specific expected result is: rapid feedback is available while high-risk decisions still carry adequate evidence.
Incorrect Answers
Adding regression checks to each story improves ongoing iterative-development coverage. The one-day prototype instead suffers from heavyweight approval that delivers feedback too late; reviewing documentation depth against risk and delivery cadence is the relevant preventive practice.
Tracking flaky-test incidence and maintain escalation for suppressed checks supports continuous delivery risk. In the source scenario, a team uses a heavyweight approval script for a one-day prototype and receives test feedback after the prototype is obsolete; the preventive practice is to revisit documentation depth when product risk or delivery cadence changes.
Keeping boundary-focused unit checks near the component source supports component testing. In the source scenario, a team uses a heavyweight approval script for a one-day prototype and receives test feedback after the prototype is obsolete; the preventive practice is to revisit documentation depth when product risk or delivery cadence changes.