How Installed-version Evidence Is Reported

Installed-version evidence confirms the laboratory actually reached the selected target and later confirms whether production push/rollback reached the expected live version.

During laboratory testing

QCUL records the starting installed version, selected target, and resulting installed version after Joomla Installer/core finalization. A mismatch prevents the test from being treated as a clean completed result.

During production work

Before push, QCUL checks the live starting version still matches the tested assumption. After push it verifies the target. After rollback it verifies the prior version using both database/manifest information and actual on-disk extension/core manifest evidence where applicable.

Why this matters

Version evidence catches partial/failed installs and prevents a stale test from being applied to a production site that has already moved to a different starting version.

Read evidence in context

Use How Installed-version Evidence Is Reported together with the other evidence for the same tested item. A version check, route check, log message, screenshot, or file/database diff is strongest when it agrees with the surrounding evidence and your own reproduction in the private laboratory; no single signal should be treated as universal compatibility proof.

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.