Testing a Joomla Core Update in the Laboratory

Joomla core rehearsals use the same Test Updates UI but a dedicated core-update adapter that resolves Joomla Update metadata, installs the captured core package only in the laboratory, and verifies the real Joomla manifest version afterward.

Location: Joomla Administrator → Components → QC Update Laboratory → Laboratory.

Step-by-step procedure

1. Refresh Test Updates and locate the Joomla core row.
2. Confirm the production/laboratory Joomla versions and the offered target version.
3. Select Test in Lab.
4. QCUL resolves the core package through Joomla Update metadata, captures/hashes it, saves a lab restore point, installs it in the lab, and runs validation.
5. Open both laboratory frontend and administrator and test critical site workflows.
6. Download the report, use Undo Lab Update once, verify restoration, and retest the core package before considering a production core push.

Why core review is broader

A core update can affect templates, authentication, menus, editing, media, forms, mail, cache, third-party extensions, and Scheduled Tasks. A simple homepage 200 response is not enough; review both public and administrator workflows and use the report/undo/retest cycle before live deployment.

Keep the evidence chain intact

The value of Testing a Joomla Core Update in the Laboratory 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.