Quality validation · Test planning Available now

Requirements become a plan.

Create a plan from feature lists, requirements, wireframes, and active cases. Record what to validate and what to defer, with the reasoning behind each choice.

Request a demoExplore the platform

You can draft a plan with active cases alone.

Test plan

Every plan has a rationale.

The name, description, rationale, Markdown plan, and selected cases live in one document. Trace each check back to the requirement that prompted it.

  • Read feature lists, requirements, wireframes, WBS, and permission matrices
  • Attach DOCX, XLSX, PPTX, PDF, images, or Markdown
  • Choose which active cases to include in this plan
  • Keep the plan in Markdown, ready to share

Requirements coverage

See the requirements left uncovered.

Requirements coverage is the share of testable statements from your documents backed by actual execution. Planning reveals which statements still have no cases.

  • Requirements coverage target: 80%
  • Checklist coverage: executed checks across 17 categories
  • Screen coverage: collected screens that have never been opened
  • Below target, the verdict is CONDITIONAL even if every check passes

Review and approval

People finalize the plan.

A plan starts as a draft, becomes active after review, and is archived after release. With Managed QA, experts review the plan and add missing checks.

  • Status: draft · active · archived
  • The QA lead approves and activates the plan
  • Ask experts to review plans and write release notes for the scope you need
Talk about managed QA

Workflow

From documents to your first run.

Set up a project, create a plan, and feed execution results back into the next plan.

  1. Set up the project

    Connect a GitHub repository and register the target URL and test accounts. The platform automatically identifies web, Android, iOS, macOS, Windows, or server/API projects.

    Typically 5 minutes

  2. Screen collection

    Explore the site to collect its screens. Server/API projects skip this step and proceed to API validation.

    Up to 90 seconds

  3. Add documents

    Attach feature lists, requirements, wireframes, environment details, and permission matrices. Testable statements extracted from these documents form the denominator for requirements coverage.

  4. Generate a plan

    Documents and active cases produce a name, description, rationale, plan, and selected cases. The plan begins as a draft.

  5. Review and activate

    Your team or an expert reviews the rationale, adds missing requirements, and activates the plan. The active plan becomes the basis for execution.

  6. Execute and replan

    Results and requirements coverage inform the next plan. Archive the plan after release and create the next one.

Frequently asked questions

Questions about test planning.

Can we create a plan without organized requirements?
Active cases are enough to create a draft without documents. Requirements coverage, however, uses statements extracted from documents. Even a single feature list makes the rationale much more concrete.
What format is the plan stored in?
The plan is a Markdown document stored with its name, description, rationale, and selected cases. View it in your workspace or copy it to share.
Who reviews the plan?
When your team uses the platform directly, a QA lead reviews and activates drafts. With Managed QA, experts review the plan, add missing checks, and continue through release notes.
How do existing document tools and cases fit in?
Attach files exported from your tools: DOCX, XLSX, PPTX, PDF, images, or Markdown. Register existing cases as manually written cases and include them in plans.
Can we manage multiple client projects at once?
Each project has its own plans. Organization workspaces show only that organization's projects and results. Development agencies and systems integrators can keep plans and verdicts separate for each client.
What changes when a plan is activated?
Selected cases in the active plan guide automated execution rules. Results update requirements coverage and the release verdict. Below 80% coverage, the verdict remains CONDITIONAL even if all checks pass.

Start a demo with your requirements.

Bring your feature list or requirements document and see how it becomes a test plan in the demo.

Request a demoImplementation consultation

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