What is a Conditional Step?
A Conditional Step (If) evaluates a condition during a Test Run and determines the next action based on the result.
Instead of always executing steps sequentially, a Conditional Step allows your Test Case to react dynamically by stopping the run or jumping to another step.
When to use it
Skip steps when a condition is met.
End the Test Run immediately when a condition is met, for example when an error message is visible.
Jump over steps and continue later in the Test Case when a condition is met.
How to add a Conditional Step
Open your Test Case.
Click Add a new step.
In Step type, select Conditional Step (If).
Configure the Step
Condition: Define what should be evaluated.
Conditions can check the presence, visibility, state, or value of elements, and can also use variables.
Examples:
Cookies banner appears
Login button exists
Submit button is disabled
Error message is visible
Page URL contains
/dashboardText equals “Welcome back”
Displayed username matches
[USERNAME]
When the condition is met, the Conditional Step can:
Stop: End the current Test Run immediately.
Go to: Jump forward to another step in the same Test Case.
- This option is available only if there are steps present after the Conditional Step.
- Choose the target step you want to continue from.
- When the jump happens, all steps between the Conditional Step and the target step are not executed and marked with a Skipped status.
If the condition is not met, the Test Case continues with the next step as usual.
Check the condition on the screen only
By default, a Conditional Step finds the element it checks in the page. When that element is hard to tell apart, for example lookalike buttons, a canvas, a chart or a game, you can make the step find it only from what is visible on the screen:
In the step dialog, open Advanced settings.
Turn on Find the element using only visual processing.
Save the step.
The steps list then shows an eye icon after the condition. Hover it to read "Finds the element using only visual processing". A step set this way is significantly slower, and each of its actions costs twice the credits, so use it only where the default fails. The same setting is available on AI steps, and the change shows in the history of the Test Case.