Quality assurance · Test case generation Available now

Screens and documents become test cases.

Create cases with scenarios, preconditions, inputs, and expected results from collected screens, registered documents, and repository code. Discard unverifiable drafts and fill the gaps.

Request a demoExplore the platform

Manage human-authored, document-based, and code-based cases in one table.

Case table

Three sources. One case table.

Cases written by people, generated from documents, and proposed from code share one table. Consistent fields let you execute and assess them in the same way, regardless of source.

  • Scenario · Preconditions · Inputs · Expected results
  • Priority: low · normal · high · critical
  • Automation level: manual · candidate · automated
  • Deduplicate cases and translate them into Korean, English, and Japanese

PR-based suggestions

Case suggestions for every PR.

Repository changes generate suggestions to add, update, or remove cases. A person approves or rejects each suggestion; only approved cases become active.

  • Connect a GitHub repository to analyze changes by PR
  • Suggest additions, updates, and removals based on changed screens and flows
  • Keep approval history and track adoption in quality trends
  • Receive browser notifications when case suggestions arrive

Verifiability

Keep cases you can actually verify.

Drafts with unreachable screens or unverifiable expected results are filtered out and rebuilt. The goal is executable coverage, rather than a larger case count.

  • Compare against collected screens to exclude unreachable flows
  • Regenerate drafts that lack expected results
  • A case counts toward coverage only after it has run
  • Managed QA experts fill gaps through exploratory testing and maintain cases
Talk about managed QA

Common checklist

Cover all 17 categories.

Keep essential checks in a shared checklist. Checklist coverage shows whether each category has checks backed by actual execution.

Authentication

Login · Logout · Password reset · Account lockout

Sessions

Expiry · Concurrent login · State after re-login

Input validation

Format · Length · Boundaries · Special characters · Required fields

CRUD

Create, read, update, delete, and order dependencies

Search and filters

Combined conditions · No results · Reset · Sort

Pagination

First/last page · Page size changes · Persistent sorting

Data integrity

Read after save · Concurrent edits · References

Files

Upload · Download · Type and size limits

Permissions

Role-based access · Direct access to unauthorized URLs

Notifications

Delivery conditions · Content · Read status

Responsive UI

Layouts at mobile, tablet, and desktop widths

Accessibility

Keyboard navigation · Focus · Alt text · Contrast

Localization

Language switching · Missing translations · Dates · Currency

Performance

Response times for initial views, lists, and search

Security

Input escaping · Authentication bypass · Exposed identifiers

Error handling

Failure messages · Retries · Recovery paths

Navigation

Back navigation · Deep links · State after navigation

Frequently asked questions

Questions about case generation.

Can we create cases without a test account?
If most screens require login, register a test account so screen collection can reach them. Without one, generation covers public screens, documents, and code. Register an account and collect screens again to fill the remaining gaps.
What does code-based generation read from a repository?
It reads code and PR changes from repositories connected through the GitHub App to suggest cases. Suggestions become active only after human approval. Repository access and data handling are described in Deployment & data handlingfor data handling details.
Who reviews generated cases?
When your team uses the platform directly, testers write and review cases, and a QA lead approves them. With Managed QA, experts review drafts, fill gaps through exploratory testing, and maintain the cases.
What happens to cases managed in spreadsheets?
Register them as manually written cases in the same table. They retain priority and automation levels and count toward execution and coverage when included in a plan.
What is an automation candidate, and who automates it?
Cases have three automation levels: manual, candidate, and automated. Candidates can run through UI or API validation. Once connected to execution, they become automated. Track automation rates weekly in quality trends.
What gets translated into Korean, English, and Japanese?
Translation is per case, preserving the structure of scenarios, preconditions, inputs, and expected results. Development agencies and systems integrators can report to international clients using one set of cases.

Your first run in about five minutes.

Connect a repository and register a target URL. Screen collection, case generation, and your first run typically take five minutes. See it on your staging environment in a demo.

Request a demoTalk about managed QA

sales@qoretix.com+82-33-242-0210Weekdays, 10:00–18:00 KST