Refreshing a Laboratory from the Current Live Site

Refresh Laboratory replaces the current copied environment with a new production-derived copy so later testing reflects the current live files/database rather than a stale lab.

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

Step-by-step procedure

  1. Download any report/evidence you need before refreshing.
  2. Open the active Laboratory workspace and select Refresh Laboratory.
  3. Confirm the destructive refresh. QCUL removes the current copied environment while preserving the appropriate completed evidence record.
  4. Keep the page open as a fresh production-derived copy is created with the current live files/database.
  5. Retest any update you still plan to push; a test performed against the old copy is not a substitute for testing the refreshed state.

What refresh invalidates

Lab restore points belong to the copied environment being removed. Any update that still matters should be tested again in the refreshed lab. Completed historical evidence can remain retained separately, but it is not proof about the new copy.

Safety check before update testing

Before relying on Refreshing a Laboratory from the Current Live Site, confirm the private copy still shows laboratory identity, its access gate works, and ordinary browsing stays inside the lab rather than silently using production. The cloned site contains production-derived data, so a laboratory that is not demonstrably isolated should be repaired or refreshed before any update rehearsal.

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.