Pause test execution for a specific duration
The Pause step allows you to temporarily halt a test for a defined number of seconds.
You can configure a pause between 1 and 60 seconds, giving you precise control over timing during your automated flows.
While DoesQA includes smarter waiting strategies for most interactions, there are scenarios where an intentional delay is useful.
When a pause makes sense
In general, condition-based waiting is preferred over fixed delays. However, there are legitimate cases where a timed pause is helpful:
Simulating real user pacing
Allowing background processes to complete
Waiting for external systems to catch up
Demonstrating behaviour during presentations or recordings
Giving time for animations or long transitions in specific environments
A controlled pause ensures your test waits exactly as long as needed.
Simulating real-world behaviour
Some systems behave differently under rapid automated input compared to real user interaction.
Adding a short pause can help you:
Reproduce production-like timing
Test rate-limited workflows
Validate timeout behaviours
Observe dynamic UI changes
Used thoughtfully, this can make your automation more realistic.
Keeping timing predictable
Because Pause is explicit and visible in your flow, it avoids hidden timing assumptions.
Your test clearly documents that a delay is intentional, making it easier for teams to understand:
Why the delay exists
Whether it is still required
Where it impacts execution time
Best practice
Use Pause when you need fixed timing control.
Use condition-based steps when you are waiting for something specific to happen.
Combined with DoesQA’s broader waiting and validation capabilities, Pause gives you full control over execution timing without compromising clarity.