An acceptance test fails because the requirement was wrong. What should happen?
Requirement validation failureSeparate correct implementation from an unsuitable requirement. Update the requirement through the authorized process and reassess affected work instead of forcing the test to approve an unusable result.
What to do now
- Confirm the implemented behavior
- Validate the real business need
- Assess the requirement correction's impact
- Approve and verify the revised outcome
When to escalate
The incorrect requirement affects essential operations or obligations.
The acceptance authority and relevant quality owner
Example
A correctly implemented approval threshold is revised after users demonstrate that the underlying policy interpretation was wrong.
Mistake to avoid
Changing the test result to pass while leaving the business problem unresolved.
Prevent a repeat
Check that closure evidence proves the agreed outcome instead of relying only on a completion percentage.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Attach acceptance criteria and test evidence to the deliverable or task, then record the authorized review decision. See the platform
Related cases
- The supplier provides a certificate but no test evidence. Is that enough?Unverified assurance evidence
- How should we handle conditional acceptance?Uncontrolled acceptance conditions
- Our integration works in isolation but fails end to end. Why?Local completion without system verification
- The requirements say the system must be user friendly. How can we test that?Untestable requirement