A Standard Test Plan organizes Test Cases for one Jira work item or one Test Folder. Use it to plan who will test, arrange the Test Cases, and track execution results across one or more iterations.
Choose a Standard Test Plan when your testing is focused on a single requirement or folder, such as validating a feature or running a folder’s regression tests for a release.
How a Standard Test Plan works
Part of the plan | Purpose |
Source requirement | The Jira work item or Test Folder the plan is based on. |
Linked Test Cases | The Test Cases and versions selected for testing. You can manage their order and assignments in the plan. |
Iteration | One round of testing within the plan. Each iteration has its own execution results and properties. |
Test Runs | The individual Test Case executions recorded within an iteration. |
Execution properties | Environment, Version, and Sprint values that provide context for the testing, when enabled. |
Creating a plan also creates its first iteration. You then execute the linked Test Cases to record results; creating the plan by itself does not execute them.
Example of a Standard Test Plan with linked Test Cases and their results.
Create a plan from a work item or folder
Start from the requirement you want to test and select the Test Cases to include. Give the plan a meaningful name, such as Login regression — November release, and set the relevant execution properties.
Follow the guide for your starting point:
You need access to the Jira space and the relevant Vansah permissions to create plans, manage their Test Cases, or execute tests.
Manage the Test Cases
Open the plan to review its linked Test Cases. Depending on your permissions, you can:
Link existing Test Cases, including cases from other Jira spaces you can access.
Create additional Test Cases when you find missing coverage.
Assign Test Cases to the testers responsible for executing them.
Update details such as priority and linked work items.
Arrange the Test Cases in the order you want to test.
To reorder Test Cases, clear active filters, sort by position in ascending order, and collapse any expanded Test Case rows before dragging a row to its new position.
Test Cases are linked records. Review changes to their content carefully because the same Test Case may be used elsewhere in Vansah.
Use iterations for repeated testing
An iteration is a separate round of testing within the same plan. For example, use one iteration for the initial release test and another for testing after fixes.
Open the Test Plan and select the iteration you want to use.
Review the iteration’s dates and Run Setup values, including Environment, Version, and Sprint where enabled.
Execute the Test Cases and review the results for that iteration.
When you need another round of testing, select New Iteration from the iteration selector.
Check the selected iteration before recording or reviewing results. A new iteration gives you a separate set of execution results while keeping earlier iterations available for review.
Find and review your plans
Open Test Plans on the Vansah Board to find plans in the Jira space. Open a plan to review its Test Cases, selected iteration, results, and execution details.
The Test Plans tab provides a central list of plans and their requirements.
When to use an Advanced Test Plan
Use an Advanced Test Plan when you need to organize testing across multiple Jira work items or Test Folders in one plan. See Creating an Advanced Test Plan.