Question 230
At fictional Ridgeway Utilities, the quality team is reviewing a change to its customer billing interface. A story is implemented with no shared examples of how a fee exception should behave. Which recurring practice would most directly reduce the chance of this situation recurring?
Explanation
Correct Answer
The recurring safeguard is to agree on concrete business acceptance examples with stakeholders before implementation. The specific expected result is: the feature is accepted against examples that were jointly defined before coding.
Incorrect Answers
Including relevant nonfunctional risks in early design reviews supports shift-left testing. In the source scenario, a story is implemented with no shared examples of how a fee exception should behave; the preventive practice is to review acceptance examples as part of story readiness.
Tracking flaky-test incidence and maintain escalation for suppressed checks supports continuous delivery risk. In the source scenario, a story is implemented with no shared examples of how a fee exception should behave; the preventive practice is to review acceptance examples as part of story readiness.
Requiring change-impact test assessment for schema, platform and infrastructure updates supports maintenance testing. In the source scenario, a story is implemented with no shared examples of how a fee exception should behave; the preventive practice is to review acceptance examples as part of story readiness.