Skip to main content

Test Plans

Test plans are reusable collections of test cases. They act as blueprints for recurring execution—smoke packs, regression suites, release criteria, or customer-specific checks.

Building a test plan​

  • Fields – Title, description, optional tag list, and a curated set of test cases drawn from any suite in the project.
  • Ordering – Drag cases to define execution order; runs inherit the sequence so testers follow the intended path.
  • Tags – Label plans (e.g., release, smoke, accessibility) to filter when creating runs.
  • Traceability – Each case retains its linkage to requirements, personas, and automation metadata when included in a plan.

Using plans in test runs​

  • When creating a run you can select a plan to auto-populate the case list. You can still add/remove individual cases before launch.
  • Plans stay in sync—if a case changes (new revision, workflow state), the run pulls the latest approved revision at execution time.
  • Combine plans with environments, milestones, or configurations to schedule regular cadences (nightly smoke, pre-release regression).

Maintenance tips​

  • Review plan membership when test cases are deprecated or moved across suites.
  • Use tags plus filters to expose “required for release” plans in dashboards and analytics.
  • Export plans alongside runs for audit or compliance reporting.