Understand Interval Time and Sleep Time
Understand Interval Time and Sleep Time
Interval time and sleep time both affect execution pacing, but they should be used carefully. Prefer condition-based waits when the test needs to wait for application state, and use timing settings only when pacing is the actual test objective.
Concepts
- Interval time controls spacing or pacing between repeated activity, depending on the execution configuration.
- Sleep time pauses execution for a fixed duration.
- Fixed waits can hide real application issues and make tests slower than needed.
Good practices
- Use Scenario Editor conditional waits for page readiness, element state, and asynchronous behavior.
- Use fixed sleep only when the delay itself is required by the business or system workflow.
- Keep wait values documented and review repeated timeout failures before increasing them.
- Validate timing changes with a small execution before scaling.
Last updated: September 9, 2026