Why do some test runs take so long?
For various reasons, it can take a long time for Autify to run tests.
In this article, you will find two common examples.
A step takes longer than 30 seconds to complete
Autify's AI waits a certain period of time (30 seconds by default) until an element that is an exact match to the last test run appears. Therefore, if the characteristics of the target element are different from those of the element at the time of recording, or are not an exact match to the element in the last successful test execution, it may take longer than 30 seconds for the step to complete.
In this case, there are two ways to make the step execute faster.
1. Add a locator to the step that takes longer than 30 seconds.
Adding a locator can save time because specific elements can be selected without relying on Autify's AI.
Note that the AI's search feature does not work in steps that include a locator, so if the target element's CSS selector changes (such as when the site is revamped), the element will not be found and the test will fail.
For more information on the locator feature, please refer to the following document:
2. Shorten the AI's wait time (default is 30 seconds).
When executing a test for the entire Workspace, you can shorten the time it takes for the Autify maintenance AI to kick in.
Note that although this may speed up the execution of steps that involve the Autify's maintenance AI, if the page always takes a long time to load, the step would be executed before the page finishes loading, which may cause the test to fail.
If you would like to use this solution, please contact our support team with the following information. We will implement it on our end.
- The number of seconds you want the AI to wait.
- The date you want the change to take place.
The test takes a long time on real device environments
In general, it takes longer to run a test in the real device environment than in the Autify Cloud environment.
However, there is a way to run tests faster in real device environments. Please refer to the document "Run Tests Faster on Real Device Environments" for details.
If you find that test execution is still slow after implementing the solutions described in this article, or if you have any questions, please contact our support team.