Completing the Production-readiness Review

Production readiness combines the completed exact-package laboratory test, explicit human review, live-site safety rechecks, and a deliberate production-protection choice.

Step-by-step procedure

  1. Open the tested update and confirm automated testing completed.
  2. Open the laboratory and complete the human review that matters to this site.
  3. Record I reviewed this update in the laboratory.
  4. Choose one production protection method.
  5. Run Check Production Now when you want to refresh readiness before the push.
  6. Resolve any exact-package, starting-version, identity, permission, worker, storage, or protection failure before selecting Push to Production.

Readiness is current, not historical

A test that was valid yesterday can become blocked today if the live starting version changed, the exact package disappeared/changed, the target is no longer production, permissions changed, or another QCUL operation is active. Check the current result immediately before push.

Production change rule

For Completing the Production-readiness Review, the live site should change only through the explicit tested-item production workflow after current readiness checks pass. Do not substitute a new package, skip the review/protection decision, or run a second production action while QCUL already owns an active push/rollback state.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.