Execute a Test Case in Vansah to record what happened when you tested it. You can work from a Jira work item, Test Folder, Test Plan, or the Test Case screen, then review the results and evidence in a Test Run.
Before you begin
Make sure you can access the Jira space and Test Case.
You need the relevant Vansah permissions to execute Test Cases and record results.
Check that the Test Case is not blocked in the execution context.
Review the Test Case version and test data before starting.
Complete any Environment, Version, or Sprint values required by the Jira space’s Test Run settings.
Choose where to start
Starting point | Use it when | Guide |
Jira work item | You are validating a story, requirement, or bug and want the execution associated with it. | |
Test Folder | You want to test related cases organized in a folder. | |
Test Plan | You are testing a planned scope in a particular iteration. | |
Test Case screen | You are reviewing one Test Case and want to select its execution target. |
Check the selected requirement or folder and, for a Test Plan, the iteration before recording results. Separate executions can have different outcomes for the same Test Case.
Choose how to record the execution
Option | What it does |
New Test Run | Creates a separate execution record. Use it for a new test or retest. |
Edit Test Run | Opens an existing execution so you can review or continue it. This option is available when a run exists. |
Quick Test | Records a selected result without walking through each step. It is available when enabled in your Jira space. |
If Quick Test shows Update Last Test Run, check its selection before choosing a result. Selected updates the displayed run; cleared creates a new run. Use a full Test Run when you need to record different outcomes for individual steps.
Record a Test Run
Open the Test Case in the work item, folder, or plan you want to test.
Use its execution control and choose New Test Run, or open an existing run when continuing the same execution.
Review Run Setup and enter any required execution properties.
Perform the test actions and select the appropriate result for each step.
Record the observed outcome in Actual Result and add relevant screenshots, files, or linked work items.
Review the overall result and remaining steps before treating the execution as complete.
Vansah records step outcomes in Test Logs within the Test Run. For a multistep case, the overall result reflects the individual step results and whether testing is complete.
Example execution with an actual result and screenshot attached as evidence.
Review the results
Open the run to check its outcome, tester, tested date, execution properties, step logs, and evidence. See Understanding and Viewing Test Runs.
A run can show an in-progress result while steps remain Untested. For the meanings of Passed, Failed, Blocked, and other outcomes, see Understanding Test Results and Statuses.
Send results from automation
You can also record executions from your test automation or development environment. Use the Test Run API or follow Sending Automated Test Results from CI/CD.
If execution is unavailable
Check your execution permissions, whether the Test Case is blocked, and whether it is still linked to the selected requirement. For a plan, also check the intended iteration. If Quick Test is missing, ask your space administrator to check its setting.