Understanding Passed, Warning, and Failed Test Results
QCUL compresses automated test evidence into administrator-facing result states so you can quickly distinguish a clean automated pass from a condition that still requires investigation.
Current result meaning
| Result | Meaning |
|---|---|
| No problems found / Passed | The configured automated checks did not identify a problem; human review is still required. |
| Review recommended / Warning | The package installed/tested but one or more evidence checks deserve administrator review. |
| Failed / Error | QCUL did not establish a valid completed test result; do not push it as production-ready. |
A pass is not certification
Automated checks cover version, selected routes/content/structure, logs, browser evidence where available, and file/database changes. They cannot know every business workflow, account role, payment path, webhook, or third-party integration on your site.
Use the tested row
Expand the tested update, use View Problems when present, open the lab, download the report, and perform the human acceptance checks before recording “I reviewed this update in the laboratory.”
Keep the evidence chain intact
The value of Understanding Passed, Warning, and Failed Test Results 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.