Why does a passing build not prove the product works?
A build catches compilation and packaging failures but does not verify a real user journey. API contracts, sessions, persistence and visible behavior need separate evidence.
How to check it
- Identify the user action affected by the change.
- Exercise success and failure paths in a real browser.
- Read the response and persisted record, then compare them with the screen message.
Concrete example
Example: an application form may compile while its server returns 403. A success toast is insufficient; the record must exist and remain correct after reload.
Avoid a false conclusion
Label fixture tests separately from live checks. A mocked response is not evidence of real delivery or payment.
Reference
VCT Editorial