Latest News from the Thunders Product Team
New feature
Run statuses that distinguish missing setup from a test verdict
Shared by Ines
•
A test that cannot start because its configuration is incomplete needs a different response from a test that finds a problem in your application. Run statuses now make that distinction clearer, and conditional steps can end a test with an outcome that matches the situation.
- Not Runnable identifies missing prerequisites, such as an unresolved application URL, variable or file variable. The pre-run check lists the missing values so you can correct the selected environment before executing.
- When authoring a conditional step with a Stop action, choose Success, Failed, Inconclusive or Skipped. For example, use Failed when an error condition is a product failure, or Inconclusive when an external dependency prevents a verdict.
- The selected outcome applies when the condition is met. A false condition continues the test, and cleanup steps still run after a conditional ending.
- Stopped is reserved for a person stopping a run. Existing conditional Stop steps without a selected outcome end new runs as Inconclusive; their past results are unchanged.
- iOS run checks also identify unsupported Android-only actions, including Wi-Fi, mobile data and location-services toggles, and show the affected steps.
#Sprint34