Reading Production, Laboratory, and Available Version Columns
The Live Site, Laboratory, and New Version columns let you confirm that QCUL is about to test the intended transition rather than simply showing “an update exists.”
Read the version trio
| Column | Read it as |
|---|---|
| Live Site | What production currently reports for this extension or Joomla core. |
| Laboratory | What the private copy currently has; it can differ after a test/undo/refresh cycle. |
| New Version | The target Joomla currently offers through update metadata. |
Common interpretations
- If Laboratory already meets/exceeds New Version, the row can say Already installed in lab rather than offering another test.
- A retained tested result can remain visible even after Joomla removes the update from its current update cache.
- After production rollback, the Live Site column can show the restored version while the row remains available for report/retest context.
Before clicking Test in Lab
Make sure the starting version and target are the pair you actually intend to rehearse. If production changed since lab creation, consider refreshing the laboratory so its starting state represents the current site.
Keep the evidence chain intact
The value of Reading Production, Laboratory, and Available Version Columns depends on preserving one traceable transition: known starting version, one selected update, exact captured package/hash, resulting laboratory version, automated evidence, and human review. Avoid manual package installs or unrelated lab changes that make that chain ambiguous before a production decision.
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.