Vansah connects reusable Test Cases with the Jira work items they cover and the results recorded during testing. A typical workflow is to prepare tests, link requirements, plan the work when needed, execute tests, follow up on defects, and review coverage and progress.
You can execute tests directly from a Jira work item or Test Folder. Use a Test Plan when you want a defined testing scope and repeatable iterations; a plan is not required for every execution.
See how the main parts connect
The diagram shows the main relationships. Test Cases describe what to test; Test Runs record what happened during a particular execution. Defects are Jira work items created or linked by a tester.
Part | Purpose |
Test Repository and Test Folders | Organize and find reusable Test Cases in a Jira space. |
Test Case | Describe a scenario to test, with the script, expected results, and supporting information. |
Jira work item | Represent the requirement or other work that the Test Cases cover. |
Test Plan and iteration | Define a testing scope and a particular round of planned testing. |
Test Run | Record execution results and evidence for a Test Case in its testing context. |
Defect | Track a problem in Jira and link it to the execution where it was found. |
Reports and dashboard gadgets | Review coverage, execution progress, results, and linked work items within a chosen scope. |
Video overview: Simplify Testing and Quality in Jira.
1. Create and organize Test Cases
Start in the Test Repository or from a Jira work item. Write a clear headline, add the test instructions and expected results, and include the data a tester needs. Use Test Folders to group related cases by feature or business process.
For example, create DEMO-C46 to check that a customer can place an order. Keep the instructions reusable so the same case can support later testing.
Get started with Create a Test Case in a Test Folder or Create a Test Case from a Jira Work Item.
Video: Test Repository Overview. Video layouts may differ from the current interface.
2. Link tests to requirements
Link the relevant Test Cases to the Jira work items they validate, such as stories, tasks, or bugs. This establishes coverage and makes it easier to see which tests support each requirement.
For example, link DEMO-C46 to the checkout story DEMO-123. Review the linked case version. Linking a case establishes coverage; it does not record a test result.
See Link Test Cases to a Jira Work Item. You can reuse cases from another Jira space when you have the required access.
3. Plan the testing when needed
Use a Test Plan when you want to organize a round of testing, assign work, and repeat it in iterations. Select the cases and requirements that belong in that scope.
Plan type | Use it for |
Standard Test Plan | Testing associated with one Jira work item or one Test Folder. |
Advanced Test Plan | Combining multiple work items or Test Folders, including supported selections from different Jira spaces. |
Choose the intended iteration before testing. Complete the required Run Setup properties, such as Test Environment, release, or sprint, when your Jira space configuration requires them.
4. Execute tests and record evidence
Start a Test Run from the relevant work item, Test Folder, or Test Plan. Follow the test instructions, record the actual result, and select the appropriate result for the execution. Add screenshots, attachments, or comments when they help explain what happened.
For planned testing, check the iteration and assigned cases before starting. For repeated testing, use the appropriate new-run or iteration workflow so the result belongs to the intended round of testing.
Quick Test can record a result with fewer steps when it is available. Check its new-run or last-run behavior before using it so you update the intended execution.
5. Create or link defects
When testing reveals a problem, use the relevant step’s defect menu to create a Jira work item or link an existing one. Choose the defect type used by your team, often Bug, and review the summary, reproduction steps, expected result, actual result, and evidence.
When available, Vansah Intelligence can draft defect details for review. A failed result does not create a Jira defect automatically. After creating or linking the work item, confirm that its key appears in the execution’s linked work items.
6. Review coverage and progress
Use Vansah’s Reports area or Jira dashboard gadgets to review the testing scope. A traceability report helps connect requirements, tests, and defects; execution reports help you monitor progress and results.
Check the report’s Jira spaces, work item or folder selection, iteration, and filters before comparing totals. The same Test Case can have different results in different testing contexts. See Choose How Test Case Execution Results Are Reported when results differ between views.
A simple example from requirement to result
Create the reusable checkout test
DEMO-C46.Link it to the checkout requirement
DEMO-123.For a release testing round, include it in a Test Plan and choose the intended iteration and Test Environment. Alternatively, execute directly from the requirement.
Run the test and save the actual result and evidence.
If it fails, create or link the relevant Jira defect and confirm its link to the execution.
Review the requirement’s coverage and the testing round’s results, then plan any retesting your team needs.
Your team’s Jira access, Vansah permissions, enabled features, and required fields determine the options available at each stage. For unfamiliar terms, see Vansah Terms and Concepts.