Ana içeriğe geç
Versiyon: 1.0.7

Test Plans

A Test Plan is the top-level quality grouping in TestPilot. It contains one or more Test Runs and summarizes their current health, progress, recent activity, and timeline.

Create a plan

  1. Open Test Plans and select New Plan.
  2. Enter a Plan Name and Plan Description.
  3. Choose Type, Platform, Environment, Priority, Start Date, and End Date.
  4. Review the draft and select Create Plan.

Configured Test Plan draft

The new plan initially contains no runs and no execution progress. Continue to Test Runs to create a bounded cycle and assign cases.

Find and interpret plans

Search by name, then use:

  • All Status to filter calculated health such as Healthy, Warning, or Critical.
  • Active Plans, Archived Plans, or All Plans to control lifecycle scope.
  • Created Date, name, or progress sorting to compare plans.
  • List or card view according to the fields you need to compare.

Test Plan list and quality summary

The list summary reports the number of plans, healthy plans, and average pass rate for the current filter. Plan rows show scenario/run counts, last-run state, health, and progress.

Expand a plan to review its recent runs, result mix, and timeline.

Expanded Test Plan with its recent Test Run

  • View all runs opens Test Runs scoped to the plan.
  • The run view action opens the related Test Execution context.

Plan actions

Open the row menu to use Edit Plan, Duplicate Plan, Archive Plan, or Delete Plan.

Test Plan actions

ActionEffect
Edit PlanUpdates the maintained plan fields.
Duplicate PlanStarts an independent copy that must be reviewed before creation.
Archive PlanRemoves the plan from the active working list while retaining it for archived review.
Delete PlanRemoves the plan record after confirmation; the confirmation states that linked Test Runs are retained.

Read the named confirmation before committing archive or delete actions. Cancel leaves the plan unchanged.

Correct use

  • Use a plan for the broader objective and a run for one dated execution cycle.
  • Reopen saved values before relying on an earlier draft, especially type, platform, environment, priority, and dates.
  • Interpret calculated health with progress and case-level evidence.
  • Do not delete a plan as a substitute for deleting or retaining its Test Runs.