How QCUL Verifies the Live Version After a Push

After production installation QCUL verifies that the live site actually reports the selected target version; successful package execution alone is not sufficient.

Extension verification

QCUL re-reads the installed extension/package version from Joomla state/manifest information and compares it with the immutable target version from the tested item.

Core verification

For Joomla core, QCUL verifies the actual core manifest version after finalization/cleanup. Production rollback later verifies the restored previous version using database and on-disk manifest evidence where applicable.

If target verification fails

The production result is not reported as a clean validated success. If a valid temporary checkpoint exists and production changed, automatic/manual rollback can protect the site; otherwise use your selected recovery process and investigate installer/log evidence.

Production change rule

For How QCUL Verifies the Live Version After a Push, 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.