What is Skip / Enable Step?
Skip / Enable Step lets you temporarily disable a step in a Test Case without deleting it.
A skipped step stays visible in your Test Case, but it is ignored during execution.
This is useful when you want to isolate an issue, or iterate on a scenario, without losing context.
When to use it
Debug a failing Test Case by skipping one step at a time.
Temporarily disable a flaky or unstable step while you investigate.
Keep “work in progress” steps in the scenario without executing them.
What happens when a step is skipped
The skipped step is not executed in any mode.
Debug
Queued
CI
You can still read the skipped step in the editor.
You cannot toggle skip while a run is actively executing.
How to skip or enable a step (in the Test Case Editor)
Open your Test Case.
Hover the step you want to disable.
Click the Skip icon.
Enable a previously skipped step
Hover the skipped step.
Click the Enable icon.
Skip behavior for special step types
Teardown steps: can be skipped. Skipped teardown steps will not run.
Discovery steps: if a discovery step is skipped, its child steps are also skipped.
You can still enable child steps individually.
Reused Test Case blocks: skipping a reused block skips the whole block as a unit.
How skipped steps appear in Test Runs
In a Test Run, any step that is not executed is clearly labeled as Skipped.
This makes it easy to identify which steps were intentionally bypassed during execution.
