Each test case in Thunders has a Status that indicates how ready it is for execution. Understanding these statuses helps your team run only validated tests and keep the test suite organized.
Statuses explained
The table below summarizes each status and what it means for executing and managing your test cases.
Status | Meaning |
Draft | Work in progress |
In Review | Awaiting team validation |
Approved | Validated and ready for execution |
Deprecated | No longer maintained |
All test cases created before this feature was introduced are automatically set to Approved.
New test cases start as Draft.
Set the status of a test case
You can update the status in two places.
From the test case properties panel
Open any test case.
Click the status pill at the top of the properties panel.
Select the new status from the dropdown.
From the Test Cases list
Go to your Test Cases list.
Click the status badge on any row.
Select the new status from the popover.
See the status at execution time
Test run reports display a read-only Status field that captures the status the test case held at the moment the run was triggered. This snapshot is immutable — changing a test case's status afterward does not alter historical run records.
Coming soon: Execution filtering
When triggering a run, Thunders will automatically exclude test cases that are not eligible based on their status. You will see a summary of which test cases were skipped and why — so your results only reflect tests that were actually ready to run.
Troubleshooting / FAQ
I created a new test case — why is it Draft and not Approved?
New test cases start as Draft so your team can review them before they enter your regression suite. Change the status to Approved when the test is ready.
Can execution results automatically change a test case's status?
No. Execution Status (Success, Failed, Stopped, Interrupted) and Test Case Status are separate concepts. Runtime results never modify the design status.