A Test Case in Vansah represents a single unit of testing designed to validate that a specific feature, requirement, or function in your product behaves as expected.
It acts as a blueprint for how testing should be carried out describing what to test, how to test it, and what the expected result should be all seamlessly managed within Jira through Vansah Test Management.
Test Case Versions
Vansah supports Test Case Versioning, allowing teams to manage and track changes and making a version active for any requirement, folder or plan it is linked with.
Test Case Key
System Generated, every Test Case in Vansah is automatically assigned a unique Test Case Key, similar to how Jira work items use keys
Example:
Test Case Key = PROJ-C105
PROJ = The Jira Project Key, identifying which Jira project the Test Case belongs to.
C = Indicates Test Case
105 = The unique numerical identifier automatically assigned by Vansah within the Jira project, representing this specific Test Case record.
Core Elements of a Test Case
Each test case in Vansah contains structured information to ensure clarity, traceability, and effective execution:
Section | Description |
Headline | A short, descriptive title summarizing the purpose or functionality under test. |
Preconditions | Conditions or setup required before the test can be executed (e.g., “User must be logged in”). |
Description | A detailed explanation of what the test case covers or its testing objective. |
Test Script | Defines how the test is executed. Depending on the Test Type, this can include:
|
Test Case Properties
Vansah Test Cases also include configurable properties and relationships that enhance organization, traceability, and reporting:
Section | Description |
Status | Managed by Vansah, Indicates the current state of the Test Case, helping teams manage progress and visibility. Common statuses include:
|
Priority | Managed by Jira, Priority defines the importance or urgency of the test (e.g., High, Medium, Low). |
Labels | Managed by Jira, Labels help you categorize or group test cases. |
Components | Managed by Jira, Components Identify which system or application components the test applies to |
Assignee | The person responsible for maintaining or updating the Test Case against the requirement it is linked with. A Test Case can be linked with many requirements. Each requirement can have a different Assignee for the Test Case version. |
Owner | Normally it is the original creator or functional owner of the Test Case. Ownership typically indicates who is responsible for the Test Case. The same owner applies across all requirements linked to the Test Case version which is different to how the Assignee works. |
Estimated Time | An estimate in minutes required to execute the Test Case. |
Linked Test Cases | References to related or dependent test cases. |
Linked Work Items (Requirements) | Direct links to Jira work items such as Stories, Epics, or Bugs to establish traceability. If Linked to a work item the Test Case will appear within the work item under the Vansah panel. |
Linked Test Folders | Logical grouping for easier test organization and navigation. If Linked to a Test Folder the Test Case will appear within the folder. |
Linked Test Runs | References to executions where this test case has been run, including results and history |
Linked Test Plans | Connects the test case to Test Plans for structured testing cycles. |
Attachments | Supporting files used to the Test Case documentation or execution |
Custom Fields | Managed by Jira, any custom field available can be linked to the Test Case |
Example Use in Integration
If you’re running automated tests (e.g., via Selenium, Jenkins, or Postman), you can reference the Test Case Key in your script or API call to log execution results directly to the correct test case in Vansah.
{
"testCaseKey": "PROJ-C101",
"status": "PASS",
"comment": "Login functionality verified successfully"
}