Rainforest allows you to add delays between each action of your automated tests. This can help avoid using excessive wait actions for pages that frequently take some time to load or update content.
After an action executes, the test waits before starting the next step. New tests have a 2-second built-in delay between steps. Existing tests have no delay, so your test continues to function as before.
While previewing in the Visual EditorVisual Editor - A tool that allows you to write tests using precise browser interactions with a live preview. Tests created with the Visual Editor (VE) run using either the Automation Service or Tester Community., we indicate which action the Automation ServiceAutomation Service - Automated browser test execution. The quickest and most cost-effective way to get test results, powered by our network of virtual machines. is currently executing. If the action takes longer than 20 seconds to complete, we warn you that the step is likely to fail while continuing to look for the element for up to 2 minutes.
- Open a test in Rainforest.
- Click the Settings icon (gear) in the upper right-hand corner of the page.
- Click the “Change Delay” link in the Delay between actions section.
- Adjust the slider as desired to increase or decrease the delay (in seconds).
- Click the Back button in the upper left-hand corner to save your changes.
Delays in Embedded Tests
An embedded test has its own delay setting and doesn’t inherit the parent test’s setting.
Final actions in a test aren’t generally followed by a delay. However, suppose the final action in an embedded test is not the final action in the parent test. In that case, it’s followed by a delay defined by the embedded test.
If you have any questions, reach out to us at [email protected] or via the chat bubble below.
Updated 2 months ago