8.7 Avoid the Pause Actions

It is normal for the process to take some time. Particularly when there are many connected systems involved, and several events have to flow through a series of drivers.

In some environments, certain tests can take longer than expected and you might be tempted to use Pause or Delay actions to help add some delays for event processing.

However, consider instead asserting that some known attribute exists, since each such action has a Retry Count and Retry Interval setting. These actions will complete, once the result is found.

So, to add a one minute delay you can add an appropriate Assert Attribute or Value exists, and then set the retry count to 10, and the retry internal to 6000 Millisecond, and then it will try until it succeeds (thus taking the minimum amount of time required) and continue trying for a full minute. This way your tests will likely run faster than simple hard coded pauses.