Test Plans and Milestones

Test plans let you save a reusable set of cases so you don't have to pick them again every time you start a run, and milestones let you group runs under a release or deadline to track progress toward it.

What is a test plan

A test plan is a named, reusable collection of test cases that acts as a template for creating runs. Instead of selecting cases from scratch every time you start testing, you build a plan once and then create a run from it whenever you need to test that area again — for example, a "Smoke suite" or "Regression: checkout" plan you reuse every release.

Creating a test plan

Open the Plans tab in a project and click New plan. You'll need to give the plan a name (required) and, optionally, a description. Then choose which cases belong to the plan using one of three modes:

• all — every case in the project
• folders — every case inside the folders you pick
• manual — hand-pick individual cases from a two-panel picker

An empty selection is allowed — the plan is simply created with no cases, and the dialog warns you before you confirm.

Note that all and folders are resolved into a fixed list of cases at the moment you save. If you add more cases to a project or folder later, the plan does not pick them up automatically — its case list stays exactly as it was when saved.

Viewing and editing a plan

Each plan has its own detail page showing its name, description, and case count, along with the list of cases it contains (each linking to the case itself). From the ⋯ menu you can:

• Edit — change the name, description, or the case selection itself (the picker opens pre-filled with the current cases)
• Delete — remove the plan; this does not delete or affect the cases it contained

If a case is deleted from the project, it's automatically removed from any plans that referenced it — the plan itself is unaffected.

Creating a run from a plan

On a plan's detail page, click Create run to start a run using exactly the cases currently saved in the plan, in the same order. You can give the run a name (defaults to the plan's name), an optional description, and optionally assign it to a milestone or test account — there's no case picker here, since the case list comes from the plan.

The resulting run carries a Plan #N badge (shown both in the run list and on the run's own page) that links back to the plan. The plan's detail page also shows a Runs section listing every run created from it.

Deleting a plan does not delete the runs created from it — the runs simply lose their link to the plan (the Plan #N badge disappears), and their results and history remain intact.

What is a milestone

A milestone represents a project goal or release with an associated due date — for example, "Release 1.0" or "Beta cut-off". Milestones give you a way to group related runs together and see progress toward a deadline.

Creating and managing milestones

Milestones are visible to every project member, but creating, editing, or deleting one is restricted to project admins. Each milestone has:

• A name (required)
• An optional description
• An optional due date (between year 2000 and 2100)
• A status: active, completed, or archived

Milestones appear in the project with a reference like MS-1, MS-2, and so on. The list is sorted by due date, with milestones that have no due date shown at the end.

Linking runs to a milestone

You can optionally assign a run to a milestone when creating or editing it — this doesn't require admin rights, just the same permission needed to manage runs. A milestone's detail page shows all the runs currently linked to it, so you can see at a glance what's been tested toward that release.

Deleting a milestone doesn't delete the runs linked to it — they simply become unlinked, and their results are preserved.