Use Vansah to connect your Jira requirements, Test Cases, execution results and defects throughout the testing process. This guide explains a typical workflow, from understanding what to test to reviewing the evidence for a release.
You can repeat these stages as requirements change, defects are fixed or another test cycle begins.
The testing lifecycle
1. Review the requirements
Start with the Jira work items, user stories, acceptance criteria or other requirements that describe the expected behavior.
Identify the behavior, business rules and risks to test.
Clarify missing, conflicting or unclear requirements with the team.
Include relevant error conditions, boundary values and nonfunctional needs, such as performance or accessibility.
Outcome: A clear, testable scope that the team agrees to validate.
2. Plan the testing scope
Choose where the team will organize and execute the tests. A Test Plan groups testing for a release, sprint or other objective, while work items and Test Folders can also provide execution context.
Use | When it fits |
Jira work item | Test a specific story, bug or requirement and keep its coverage visible alongside the work item. |
Test Folder | Organize a reusable group of tests, such as a feature area or regression suite. |
Standard Test Plan | Plan testing for one Jira work item or one Test Folder. |
Advanced Test Plan | Bring together multiple work items and Test Folders, including supported scope across Jira spaces. |
Set the planned dates, assignment and relevant scope. Review the selected Test Cases before creating and running the plan. Use iterations when you need to repeat planned testing.
For current steps, see Creating an Advanced Test Plan and Understanding Advanced Test Plans.
The existing Vansah video introduces Advanced Test Plans:
3. Create and organize Test Cases
Review existing Test Cases first so you can reuse coverage where it fits. Create additional cases for missing scenarios, with clear titles, prerequisites, test data and expected outcomes.
Choose a script format that suits the test:
Format | Use it for |
Multi Steps | Ordered actions with an expected result for each step. |
Plain Text | A free-form test description or checklist. |
BDD – Gherkin | Behavior examples written with Given, When and Then. BDD means behavior-driven development. |
Automation | Automation code where the relevant capabilities are available in your workspace. |
Use folders, labels, priorities and other supported fields to make tests easy to find and maintain. Add attachments or comments when they help a tester understand the scenario.
Link Test Cases to the requirements or folders they cover. Vansah Test Cases are managed as Vansah records linked to Jira work items; they do not require a Jira Test Case work item type.
If you use Vansah Intelligence to help draft tests, review the generated scenarios, steps and expected results before execution.
4. Prepare the environment and test data
Make sure the application, accounts, permissions and data needed for testing are ready. Set the environment, release or sprint on the relevant execution where needed so results can be understood in context.
Note: An environment name recorded in Vansah describes where a test was run. It does not create or configure the application environment itself.
5. Execute tests and record evidence
Open the relevant Jira work item, Test Folder or Test Plan. For a plan, choose the intended iteration.
Run the selected Test Cases and follow their scripts.
Compare the actual behavior with the expected result and record the appropriate outcome.
Add actual results, comments and useful evidence, such as screenshots.
For a failure, create or link the relevant Jira defect to the Test Run so the team can trace the problem.
After a fix, retest in the appropriate run or iteration and record the new outcome.
Test automation can also submit results to Vansah through supported integrations. See Sending Automated Test Results to Vansah from CI/CD.
6. Review coverage, progress and results
Use the work item, folder and plan views to review completed testing, remaining work, failures and linked defects. Check both coverage and outcomes before deciding whether more testing is needed.
Vansah’s Jira dashboard gadgets provide wider reporting, including Test Summary, Test Execution, Burnup and traceability views for requirements, folders and plans. Choose a report that matches the question you want to answer, such as:
Which requirements still need tests?
How much of the planned testing has been executed?
Which tests failed, and what defects are linked?
How has testing progressed over the selected period?
Use the findings to update the test scope, improve Test Cases and agree on the next testing or release actions with the team.