Test Management
Test Plans
A test plan defines when and how to run tests — which cases, on what trigger, assigned to whom. Suites organize what tests exist; plans schedule and coordinate their execution against a release or sprint.
Product news and testing tips.
Why it matters
Suites answer 'what', not 'when'
A suite organizes what tests exist. It doesn't say which of them run on every commit versus once before a release.
A fixed list goes stale
A hand-picked list of test cases for "release testing" needs updating every time the suite changes, or it silently misses new cases.
No link between a plan and a release
Without a shared reference point, it's unclear whether this cycle's testing is actually tied to the release it's supposed to verify.
How it works
Create a plan from an explicit case selection, or point it at a saved dynamic query so it always includes whatever currently matches. Link it to a milestone, and its coverage and pass rate feed directly into that milestone's readiness picture.
Qualflare| Plan | Source | Status | Coverage | Milestone |
|---|---|---|---|---|
Smoke Test Plan | Dynamic query | Active | 100% | v2.8 Release |
Full Regression Plan | 42 cases | Active | 87% | v2.8 Release |
Sprint 24 Verification | 18 cases | Draft | 62% | Sprint 24 |
Q1 Compliance Sweep | Dynamic query | Completed | 100% | — |
What you get
Build from cases or from a query
Populate a plan with an explicit case selection, or a saved dynamic query — the plan automatically includes whatever currently matches.
Coverage tracking per plan
See what fraction of a plan's cases have been executed and how they resolved, not just a raw pass/fail count.
Link plans to milestones
Tie a plan to a release or sprint milestone so its execution status feeds directly into that milestone's readiness picture.
A real lifecycle
Plans move through Draft → Active → Completed, so it's clear at a glance whether a plan is still being assembled or is the one currently running.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
Frequently asked questions
What is a test plan?
A test plan defines when and how to run tests — which cases, on what schedule or trigger, assigned to whom, in which environment, and why (release verification, regression, and so on). Unlike a test suite, which organizes what tests exist, a plan schedules and coordinates their execution.
What's the difference between a test suite and a test plan?
Suites = what tests exist (organization). Plans = when to run tests (scheduling). The same "Authentication" suite might run daily inside a "Smoke Test Plan" and weekly inside a "Full Regression Plan" — one suite, two different execution plans.
Can a test plan update itself as my suite changes?
Yes, if it's built from a dynamic query instead of an explicit case list — the plan always includes whatever currently matches the query's criteria, so it doesn't silently miss cases added after the plan was created.
Which plan tier includes Test Plans?
Test Plans is available on the Core plan and above.