High-level Workflow Overview
Tip: For the best understanding of how Vansah works, read this Terms and Concepts together with the Vansah Workflow Overview.
Vansah provides an end-to-end testing framework seamlessly integrated into Jira, enabling teams to manage test assets, plan executions, track results, and generate insights all in one place.
The workflow below illustrates how the main components connect and flow together.
Test Repository
The Test Repository is the foundation of Vansah’s Test Case Management process. It maintains all Test Cases and Test Folders, forming the central library of reusable test assets.
Test Cases represent the individual testing scenarios along with details and the associated Test script type used to validate application functionality.
Test Folders provide a hierarchical structure to group and organise related Test Cases, allowing you to manage Tests by feature, release, or business process.
Relationship:
Test Cases can be linked to Jira Work Items (e.g. Epics, Stories, Tasks, Bugs) to establish full traceability.
They are also included in Test Plans, enabling execution across multiple cycles or environments.
Jira Work Items (Requirements & Traceability)
Each Jira Work Item (e.g. Epic, Story, Task, or Bug) can be directly linked to one or more Test Cases to maintain requirement coverage.
Vansah uses Test Case Linking to trace test coverage against project requirements.
This ensures visibility into what’s tested, what’s passed or failed, and which requirements are at risk.
Relationship:
Jira Work Items are covered by Test Cases.
Defects discovered during execution are logged as Bugs, closing the feedback loop between testing and development.
Test Plans
Test Plans define what will be tested and when. They act as structured containers that group Test Cases or Test Folders for execution.
Standard Test Plans link to a single Jira Work Item or Test Folder within the same project.
Advanced Test Plans can include multiple Jira items or Test Folders from different projects, providing cross-project flexibility.
Relationship:
Test Plans are created from Test Cases and Test Folders in the repository.
They are then executed through Test Executions (Test Runs).
Test Executions (Test Runs)
A Test Execution (or Test Run) represents the actual execution of the Test Case. Each run captures Actual results, comments, test data, environment details, and execution history.
Vansah supports multiple execution modes including Quick Test and Bulk Execution to accelerate validation.
Each execution generates Test Results (e.g. Passed, Failed, Blocked) and can be linked back to defects in Jira.
Relationship:
Test Executions are executed from Test Plans or directly from the Test Case against the requirement.
Failed steps are logged as Bugs in Jira for traceability.
Bugs (Defects)
When a Test Execution fails, Vansah enables testers to raise Bugs directly in Jira with all relevant test context automatically linked (test case, test plan, environment, and result).
Relationship:
Bugs are related to Test Executions and linked back to Test Cases for visibility into which tests or requirements failed.
This ensures smooth collaboration between testing and development teams.
Reports & Insights
All activities in Vansah from Test Case design to Test Execution results feed into Reports & Insights.
Vansah offers its own reporting area and supports Jira dashboard gadgets for real-time reporting of coverage, pass/fail rates, execution progress, and defect trends.
These insights empower teams to monitor quality, identify risk areas, and make informed release decisions.
Relationship:
Reports are generated from the entire testing life-cycle, consolidating data from Test Repository, Test Plans, Executions, and Bugs.
End-to-End Workflow Summary
Create and organise Test Cases within Test Folders in the Test Repository.
Link Test Cases to Jira work items to establish traceability.
Combine relevant Test Cases or Folders into Test Plans.
Execute those plans through Test Executions, recording results and raising Bugs as needed.
Review progress, coverage, and outcomes in Reports & Insights for continuous quality improvement.