Use this glossary to understand the terms you see while organizing, planning, and running tests in Vansah. For an end-to-end example, read the Vansah Test Management Workflow Overview.
Organize your tests
Term | Meaning |
Jira space | The Jira area where your team manages work. Vansah uses its space key to identify that context. API fields such as |
Vansah Board | The Vansah area for a Jira space, with access to its testing overview, Test Cases, Test Runs, Test Plans, Test Environments, and reports. |
Test Repository | The area where you organize Test Cases and Test Folders. |
Test Case | A reusable test describing what to check. It can include a script, preconditions, expected results, and supporting information. |
Test Folder | A folder that groups linked Test Cases and can contain subfolders. Linking a Test Case to a folder does not create a separate copy of it. |
Test Script | The instructions or script attached to a Test Case. Supported formats include Multi Steps, Plain Text, BDD, and Automation. |
Precondition | Something that should already be true before you begin the test, such as having an active test account. |
Expected Result | The behavior you expect when a test action is performed. |
Plan and run tests
Term | Meaning |
Standard Test Plan | A plan based on one Jira work item or one Test Folder in the plan’s Jira space. |
Advanced Test Plan | A plan that brings together selected Jira work items and Test Folders, including sources from different Jira spaces. |
Test Plan iteration | A numbered round of testing within a Test Plan, allowing the plan to be run again and its results reviewed by iteration. |
Test Run | One execution of one Test Case. It records the execution context, results, and evidence for that run. |
Test Result | The recorded outcome of a test or step. The labels you see depend on the results configured for your Jira space. See Test Results and Statuses. |
Actual Result | What happened when you performed the test, recorded as evidence or a comment on the execution. |
Quick Test | A way to record an execution result without working through the full execution page. See Record a Result with Quick Test. |
Bulk execution | An action applied to a selected group of Test Cases. Review the selected cases and execution context before applying a result. |
Defect | A Jira work item created or linked to record a problem found during testing. A failed test does not by itself mean a new defect has been created. |
The following diagram illustrates results for Multi Steps, Plain Text, and BDD runs. It shows examples rather than every supported script format.
Older diagrams use the Jira term “Project”; the corresponding area is now called a Jira space.
Manage versions and test data
Term | Meaning |
Test Case version | A version of a Test Case and its script. Check which version is selected or linked when reviewing coverage and results. |
Default Test Case version | The version marked as the Test Case’s default. This is different from the version already selected for a particular link or execution. |
Test Environment | An environment label such as QA or UAT used to organize or record the context for testing. |
Test Data | Values used while testing, such as an email address, quantity, or URL. |
Test Data Collection | A group of reusable variables and values. Collections can be managed under Test Environments or for a selected Test Case version. |
Variable | A reusable named value that can be referenced in a Test Script. |
Collection version | A separate version of a Test Data Collection’s variables and data. |
Data iteration | A numbered set of values within a collection version. It is distinct from a Test Plan iteration. |
Learn more about how Test Data Collections work and using variables in scripts.
Understand coverage and reporting
Term | Meaning |
Test Case link | An association between a Test Case version and a Jira work item, Test Folder, or plan context. It lets you reuse the case while tracking coverage. |
Traceability | The relationship between requirements, linked tests, executions, and defects. It helps you see what is covered and what has been tested. |
Jira dashboard gadget | A configurable Vansah report displayed on a Jira dashboard. Its saved scope and filters determine the information shown. |
Confluence gadget | A supported Vansah report inserted into a Confluence page from a configured Jira dashboard gadget. |
Jira workflow validator | A rule that checks a configured testing condition before allowing a Jira work item transition. See Use Vansah Test Results in Jira Workflow Validators. |
See Set Up Vansah Testing Gadgets to choose and configure a report.
Understand responsibilities and access
Term | Meaning |
Test Case owner | The person responsible for the Test Case itself, such as its design and maintenance. |
Test Case assignee | The person responsible for testing in a particular linked context. The same Test Case can have different assignees for different requirements. |
Vansah permissions | Controls that can use Jira groups to allow particular Vansah actions within a Jira space. When no groups are configured for an action, the applicable default Jira permission is used. |
Custom field | An additional configured field. Available fields and editing options depend on the feature and configuration; do not assume the same custom field is available on every Vansah item. |
Vansah Intelligence | AI assistance in supported workflows, such as drafting Test Cases or defects and reviewing report information. Review generated content before using it. |
Data residency | The region in which covered app data is hosted. For the scope and conditions, refer to Vansah’s Data Residency Policy. |
For access details, see Manage Vansah Permissions with Jira Groups and Default Jira Permissions for Vansah.