Product tour
From project setup to verdict.
Walk through repository connection, screen collection, planning, case generation, three-engine execution, and verdicts in order, using your team's repository and document setup.
Request a demoResources
See what you will receive: plans, case tables, execution reports, and a guide to reading verdicts.
Explore
Review the format of plans, case tables, and reports, then create them for your team's project in a demo.
Product tour
Walk through repository connection, screen collection, planning, case generation, three-engine execution, and verdicts in order, using your team's repository and document setup.
Request a demoSample plans and cases
Review a plan with its name, description, rationale, Markdown document, and selected cases, alongside a case table with priorities and automation levels.
View test planningSample report
Pass, fail, quarantine, and skip counts, requirements/checklist/screen coverage, quarantine status, and security findings come together in one verdict.
View reports and evidenceGuides
Learn the three verdict levels, three coverage measures, and quarantine rules needed to interpret a report.
Platform overviewSample report Available now
Staging run #48 for a commerce web project passed 45 cases and failed one, yet received CONDITIONAL. The failure was minor, one Firefox check with inconsistent results was quarantined, and requirements coverage was below the 80% target.
Sample plans and cases Available now
Cases generated from screens and requirements share the same table format as manually written cases. Unverifiable drafts are replaced, duplicates removed, and cases translated into Korean, English, and Japanese.
Guides
The first questions teams ask when they receive a report.
FAIL means critical or major failures. CONDITIONAL covers minor/trivial failures, quarantine, inconclusive checks, or coverage below 80%. PASS means every executed check passed on its first attempt.
Verdict rulesRequirements, checklists, and screens show what was not checked. This is not code coverage: a case is not validated merely because it exists.
CoverageIf repository code or secret scanning is disabled, findings show as unavailable rather than zero. Unchecked items never count as a pass.
Security testingChecks are automatically quarantined when results on the same commit flip in at least 20% of the last 20 runs. They continue running but cannot trigger FAIL.
Test reliabilityFrequently asked questions
Use your repository and documents to create a plan, case table, and first report in a demo. If you want to delegate the work, we will discuss Managed QA.
sales@qoretix.com+82-33-242-0210Weekdays, 10:00–18:00 KST