Understanding the Test Updates Table
The Test Updates table is the main update-rehearsal list inside an active laboratory, combining currently offered updates with retained tested rows that still matter for review, reports, production, or rollback.
Current columns
| Column | Meaning |
|---|---|
| Update | The Joomla core or extension/package identity. |
| Live Site | The production installed version; after push/rollback the current live result can also be labeled. |
| Laboratory | The version currently installed in the private copy, with Tested here where appropriate. |
| New Version | The version Joomla currently offers. Not available can appear when the row cannot be selected. |
| Action | Test in Lab, a retained result label, Already installed in lab, or Not available to test depending on state. |
Tested rows stay attached
After a test, a detailed row expands directly beneath the update so package identity, evidence, lab review, production protection, report, push status, and rollback controls remain tied to the exact tested item.
Use the table as a decision record
Before testing, verify the live/lab/target version pair. After testing, use the same row rather than assuming a newly refreshed Joomla update_id is the identity of the previous test; QCUL retains stable extension identity plus exact target version for historical tested results.
Keep the evidence chain intact
The value of Understanding the Test Updates Table 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.