Use a test plan to organize the test cases for a testing cycle, assign work, record results, and review progress. Iterations let you repeat the testing cycle while keeping its results separate from earlier cycles.
Open a test plan
Open Vansah in your Jira space.
Select Test Plans and open the plan you want to manage.
Check the selected Iteration before recording results or reviewing progress.
Available actions depend on your Vansah permissions. Editing a plan, linking test cases, executing tests, and deleting plans or iterations are controlled separately.
Plan type | How you organize testing |
Standard Test Plan | Work with a list of test cases for the testing cycle. See Understanding Standard Test Plans. |
Advanced Test Plan | Organize testing around requirements, such as Jira work items and test folders. Select the relevant requirement before working with its test cases. See Creating an Advanced Test Plan. |
Add or link test cases
Open the plan’s Test Cases area. In an Advanced Test Plan, first select the requirement you want to test.
Create a test case: Select the + button, enter the test case headline, and confirm. Open the test case to complete its script and other details.
Link an existing test case: Select Link, find the test case, and complete the linking dialog. You can select test cases from Jira spaces you can access, subject to your linking permissions.
Organize the test case list
Change the test case order
Clear any active test case filters.
Sort by Position # in ascending order.
Collapse any expanded test case.
Drag the test case row to its new position.
Choose and arrange columns
Use the column selector at the right of the table header to choose the information to display. Drag movable column headings to change their order. The selection and row action columns remain fixed.
Run tests and record results
Select the correct iteration and, for an Advanced Test Plan, the requirement to test.
Check the run properties, such as environment, release, and sprint. Complete any required fields.
Use the test case’s execution control to open the run, then work through the script.
Record step results, enter actual results, and add evidence where needed.
You can also use Start on the plan to begin its execution workflow. See Executing Test Cases from a Test Plan for the execution controls and navigation.
Use Quick Test
When Quick Test is enabled and available for the script type, select an overall result from the test case’s execution menu to record the result without working through the steps. Check the selected iteration before making the change.
Link a Jira work item or bug
From a test run or step, open the defect menu to create a Jira work item or link an existing one. This keeps the work item connected to the execution where the problem was found.
Review progress and insights
The plan’s progress summary shows completed and remaining testing for the selected iteration. Select the Insights chart icon to review the test summary, execution trends, and linked work items. Check the report’s date range when comparing results.
Update the plan details
Open Details to edit the plan name and review planned dates and iteration activity. Select the name, enter the new value, and confirm the edit.
Use the owner control to change who is responsible for the plan. Use Run Setup to change enabled run properties. Run Setup changes apply across the plan’s iterations, so review the existing values before changing them.
Repeat testing with a new iteration
Open the Iteration selector near the plan key.
Select New Iteration.
Review the new iteration’s dates and run properties before testing.
Switch back to an earlier iteration whenever you need to review its results. Starting another iteration keeps earlier execution records separate.
Use the plan’s actions menu
Open the three-dot menu near the top of the plan.
Action | What to do |
History | Review changes to the plan. See Viewing Test Plan History. |
Clone | Enter a name for the new plan, review the properties to copy, and select Clone. The new plan reuses test case links and starts with a new iteration; it does not copy execution history. |
Export | Review the export options and file type, then export the plan’s test cases and results for the selected iteration. |
Iteration — Manage Iterations | Use the delete control beside an iteration, then review and confirm the deletion. You need iteration deletion permission, and the plan must retain at least one iteration. |
Test Plan — Delete Test Plan | Review and confirm the deletion when you no longer need the plan. Deleting the plan does not delete the underlying test cases from the Test Repository. |
Before deleting a plan or iteration, export any results you need to retain and review the confirmation carefully. Deleting an iteration removes that testing cycle from the plan’s available iterations.
If an action is unavailable
Ask your administrator to check the permission for the specific action.
To reorder test cases, clear filters, sort by ascending position, and collapse expanded rows.
If execution is unavailable, check required run properties and whether the test case or requirement is blocked.
To investigate unexpected results, check the iteration and requirement selected in the plan.