Understanding Baseline and Post-update Evidence
Baseline evidence describes the laboratory before the selected update changes it; post-update evidence measures the same environment after installation so QCUL can attribute differences to that rehearsal.
Before installation
- Record starting extension/core version.
- Capture selected route/content/structure health.
- Snapshot relevant file/database state needed for comparison.
- Record log positions/state so later evidence can distinguish newly appended entries.
- Create the laboratory restore point used by Undo Lab Update.
After installation
- Verify target version.
- Repeat route/structure health checks.
- Compare file/database scope.
- Collect newly appended logs.
- Capture browser evidence where supported.
Why same environment matters
Comparisons are meaningful only when the laboratory starting state is coherent. If the lab has accumulated unrelated manual edits or multiple historical changes, refresh it before relying on a new baseline for a production decision.
Read evidence in context
Use Understanding Baseline and Post-update Evidence together with the other evidence for the same tested item. A version check, route check, log message, screenshot, or file/database diff is strongest when it agrees with the surrounding evidence and your own reproduction in the private laboratory; no single signal should be treated as universal compatibility proof.
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.