A Test Plan brings together the test cases you want to execute for a feature, sprint, release, or other testing activity. Use it to organize the work, assign testing, record results, and track progress.
Test cases describe what to check. A Test Plan links those cases and lets you run them in separate rounds of testing called iterations.
Where to find Test Plans
Open Vansah in your Jira space and select the Test Plans tab. Select a plan’s key or name to open it. You can also open linked plans from the Test Plans tab in a Jira work item’s Vansah Test Management panel or from a Test Folder.
Choose a Test Plan type
Type | Use it when | How it is organized |
You want to test one Jira work item or one Test Folder. | A focused case list for that work item or folder, with iterations, execution results, and reporting. | |
You want to bring several requirements into one testing activity. | Combine Jira work items and Test Folders, including those from other Jira spaces you can access. Review and execute cases by requirement. |
For example, use a Standard Test Plan to test one story. Use an Advanced Test Plan for a release that includes several stories and regression Test Folders.
Available features and limits also depend on your Vansah subscription. See Vansah Standard vs Advanced: Features and Limits.
Get started with a Test Plan
In the Vansah Board’s Test Plans tab, select + to create a plan.
Choose a plan based on a work item, a Test Folder, or an Advanced Test Plan, then select Next.
Select the required work item or folders, enter a meaningful plan name, and review the dates and other available settings.
Create the plan and open it. Review the linked test cases and versions. Add or link any other cases needed for the testing activity.
Assign the testing, execute the cases, and review progress in Insights.
You can also create a Test Plan directly from a Jira work item. Creating a plan does not record execution results; the cases still need to be tested.
Use iterations for repeated testing
Each plan starts with its first iteration. Create a New Iteration when you need another round of testing, such as retesting a fix or testing a later build.
Use the iteration selector in the open plan’s header to switch between rounds and review their results. Confirm the selected iteration before executing cases or exporting results.
Plan configuration changes can affect all iterations. For example, reconfiguring an Advanced Test Plan changes its requirements and test case scope across the plan.
Manage your testing
Open a plan to manage its cases and execution. The plan’s More options (⋯) menu and the row menu in the Test Plans list provide additional actions.
Task | What it does |
Add or link test cases | Include new cases or reuse existing ones you have permission to access. Review the selected versions before execution. |
Assign and order testing | Assign cases to testers and arrange their execution order. |
Clone a plan | Create a separate plan using the existing case links. Previous execution results are not copied. |
Export a plan | Download case information, scripts, or results for sharing and review. |
Review history | See recorded changes to the plan and its iterations. |
Delete a plan | Move the plan to the Recycle Bin. The underlying test cases remain in the repository. |
See Managing Test Plans for detailed steps. Available actions depend on your permissions.
Track results with Insights
Open a plan, select the iteration you want to review, and select the Insights icon in the header.
Use the reports to review execution progress, results, assignments, and traceability. See Viewing Test Plan Reports for the available reports and export options.