verification-discipline

To verify code beyond unit tests, you must collect real integration, smoke, or end-to-end evidence. This means confirming the system functions in a fresh environment and documenting observable proof like logs or screenshots before declaring the task done.

Pre-merge verification requires observable proof from unit, integration, smoke, or production-equivalent testing. You must document these results to confirm real system behavior rather than just checking that the code looks correct.

Defining completion criteria involves distinguishing unit test success from real integration evidence. You should use an outcome-first approach, writing tests from the user-visible result backward to validate the right behavior and document observable proof.

Passing unit tests does not guarantee completion because they only validate code correctness, not real system behavior. You need integration and smoke test evidence to prove the intended outcome works in a production-equivalent environment.

Yes, outcome-first testing fits post-implementation review by validating user-visible results backward. It guides you to confirm changes work in a fresh environment and require logs or screenshots as observable proof before closing the task.