What Happens During Extension and Joomla Core Installation in the Laboratory

Extension and Joomla core tests share one visible workflow but use the installer path appropriate to the update type inside the private laboratory.

Extension/package installation

QCUL calls the lab runtime with signed authorization, allowed package path, extension identity, target version, and expected SHA-256. Joomla Installer performs the update inside the cloned Joomla root/database prefix; its messages, warnings, and output become evidence.

Joomla core installation

The core adapter safely unpacks the captured core ZIP, rejects unsafe paths/symbolic-link behavior, copies the core tree into the laboratory, and invokes Joomla Update finalization/cleanup before verifying the actual Joomla manifest version.

After installation

• Verify resulting installed version.
• Run basic frontend and administrator checks.
• Compare files and database/schema/data scope.
• Capture relevant Joomla/PHP log changes.
• Update the tested row to Passed/Warning/Failed-style evidence state and preserve the report.

Keep the evidence chain intact

The value of What Happens During Extension and Joomla Core Installation 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.