Understanding Production Safety and Drift Checks

QCUL production safety checks focus on conditions that can make the exact tested update unsafe to replay now, while recording unrelated production drift as context rather than invalidating every test automatically.

High-value blocking checks

  • The tested item still belongs to the active laboratory and completed laboratory test.
  • The administrator review confirmation is still recorded.
  • The exact package still exists and its SHA-256 matches the tested package.
  • The live site still has the expected starting version for the selected update.
  • The current Joomla root is production, not a QCUL laboratory copy.
  • The current user has the required permission and is a Joomla Super User for production push/rollback.
  • No conflicting QCUL production operation is already running.
  • The selected production-protection method is valid and ready.
  • Storage/environment/maintenance handling are suitable before production changes begin.

What “drift” means here

QCUL can compare production context captured when the laboratory test began with the current live site. Broad unrelated site changes are useful evidence, but 1.01.14 does not treat every changed file/content item as a reason to invalidate the test.

Selected-target drift remains critical

If the live extension/Joomla starting version for the tested target changed, the production assumption is no longer the same as the rehearsal. QCUL blocks or requires a fresh test rather than applying the package to an untested starting state.

Production change rule

For Understanding Production Safety and Drift Checks, 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.