What is the defining characteristic of a vertical slice test compared to an isolated unit test suite in Helpdesk Copilot?
Day 29: Integrate the Vertical Slice and Verify Acceptance
Integrate the Vertical Slice and Verify Acceptance
Loading lesson content...
In the acceptance test above for Helpdesk Copilot, why is verifying the negative obligation (outboundMessages.length === 0) just as critical as asserting the positive presence of draftText?
A release candidate packet for Helpdesk Copilot v1.0 contains clean test logs, green unit tests, and a summary stating 'All acceptance criteria verified.' However, the security auditor notes that the candidate lacks trace identifiers, environment variable hashes, and the exact vector index snapshot SHA used during testing. Why does the lesson insist that acceptance evidence include pinned environment and version metadata?