Use a regression test cycle to check that existing behavior still works after a change. In Vansah, bring the relevant Test Cases into a Test Plan, execute them in an iteration, and review the results before deciding what to test next.
Example: checkout regression
Suppose your team has changed payment handling for a November release. Your regression scope could include a successful purchase, a declined payment, discount calculations, and order confirmation. Use the existing Test Cases for these checks and add any missing coverage.
Planning decision | Example |
Scope | Checkout behavior affected by the payment change, plus important neighboring checks. |
Source | A Test Folder such as Regression/Checkout, or several Jira work items and folders. |
Plan name | Checkout regression — November release. |
Testing round | Iteration 1 for the initial run; a later iteration for another round after fixes. |
Evidence | Step results, observed behavior, attachments, and linked Jira work items. |
Before you begin
Confirm access to the Jira space, source requirements, and Test Cases. You need the relevant Vansah permissions to create or manage plans and execute tests.
Review the scripts and Test Case versions you intend to use. Prepare the accounts, test data, and application build needed for the checks.
Agree which behavior is in scope and which unresolved issues need attention before the release.
1. Select the cases and plan type
Open the relevant Test Folder or Jira work item and review its linked Test Cases. Add missing checks or link suitable existing cases.
Choose a Standard Test Plan for one work item or Test Folder. Choose an Advanced Test Plan when the cycle needs several work items or folders.
Review the selected cases and their versions. Include the checks needed for this cycle rather than relying on the plan name to define its scope.
Follow Create a Test Plan from a Test Folder or Create a Test Plan from a Jira work item. For a combined scope, see Create an Advanced Test Plan.
2. Prepare the first iteration
Give the plan a recognizable name, such as Checkout regression — November release, and open it. Creating the plan creates its first iteration; it does not record test results.
Confirm the selected iteration, requirement, case list, and linked versions. In an Advanced Test Plan, review each included requirement.
Review the planned dates and Run Setup values, including Environment, Version, or Sprint where enabled. Complete any mandatory values.
Assign the testing and arrange the cases in a practical order. For example, check that a customer can complete a normal purchase before testing less common payment failures.
Check the scope of changes: some plan configuration and Run Setup changes apply across iterations. Read any warning before changing settings; do not assume every plan setting belongs only to the selected round.
3. Run the regression checks
Open Test Plan Execution and confirm the iteration you are testing. For an Advanced Test Plan, select the relevant work item or folder requirement.
Use a case’s Execute control and choose New Test Run for a separate execution. Perform the actions and record the step results and Actual Result.
Attach useful evidence and link relevant Jira work items when you find a problem. Record what happened so another tester can understand the result.
To work through remaining tests, use Start and review its tester scope. Continue through the selected work, or use Stop when you need to leave the active execution.
For the full execution procedure and help with blocked cases or missing permissions, see Execute Test Cases in a Test Plan.
4. Review completion and failures
Open the plan’s Insights and confirm the report’s iteration.
Use the Test Summary Report to review planned, completed, outstanding, in-progress, and blocked testing. Follow linked counts to inspect the underlying cases.
Open failed or unfinished Test Runs to review step logs, actual results, and linked work items. Decide who will investigate each problem and what needs another test.
Share or export the relevant report with the iteration and testing context clearly identified.
A high pass rate alone does not show that all planned testing is complete. Review outstanding, in-progress, and blocked work as well. See View Test Plan Reports for the report definitions.
5. Start another round when needed
After fixes or a later build, select New Iteration when you want a separate round within the same plan. Earlier iterations remain available for reviewing their execution results.
Select the new iteration and confirm its dates, assignments, and Run Setup values.
Review the case scope and versions before starting. A new iteration is another round of the plan; it is not an automatic selection of failed cases only.
Execute the checks needed for that round and review its results separately. Switch back to the earlier iteration when comparing evidence.
For broader changes to what the plan covers, review Reconfigure an Advanced Test Plan before changing its requirements. Reconfiguration can affect the plan across iterations.
Before sharing the outcome
Identify the plan, iteration, application build, and environment used for the review.
Call out missing coverage, unfinished tests, blocked work, and unresolved failures.
Use your team’s release criteria to make the release decision. Test results provide evidence for that decision.