Test at the right layers
Unit tests protect isolated logic; contract tests protect interfaces; integration tests reveal cross-module failures; E2E tests validate user journeys. Each addresses different risks.
One passing E2E test cannot replace authorization or migration verification.
Failure states are product states
Loading, empty results, validation, retry, timeout, duplicate submission and permission-denied states need usable UI and post-release observability.
On mobile, explicitly test viewports, virtual keyboards, dialogs, overflow and navigation.
Code Verified differs from Live Verified
A passing build proves that artifacts were created; a READY deployment proves the hosting platform finished deployment. Live verification requires direct access, exercising actual workflows and capturing evidence.
Production systems also need tested rollback and recovery paths.
Evidence-led release decisions
- PASS when every mandatory gate has evidence.
- PASS WITH FINDINGS when limitations are documented and accepted.
- CHANGES REQUIRED when meaningful behavior is not correct.
- BLOCKED when access, configuration or evidence is missing.