Reading the Tested-update Row and Issue Report

After a test, QCUL expands a tested-update row directly beneath the available update so package identity, evidence, human review, production protection, push, report, and undo remain tied together.

What the row can show

• Test result/status label.
• Tested package filename/size/hash evidence.
• Review Lab Site/Open Laboratory action.
• Download Report.
• View Problems/issue report when QCUL has focused findings.
• Human review confirmation.
• Production protection/readiness controls.
• Push/production result, Review Live Site, and eligible rollback controls.

Why the issue report is focused

The main table intentionally stays compact. A clean test can simply say no problems found; when a warning/failure exists, the issue report surfaces the specific evidence that needs attention rather than dumping every internal detail into the table.

Retained visibility

A tested row can remain visible after production push/rollback even if Joomla’s current updater cache no longer lists the update. That preserves the operational record and rollback/report context.

Keep the evidence chain intact

The value of Reading the Tested-update Row and Issue Report 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.