Tips for Efficient Use of your Daily Capacity
My test scripts have too many ‘Pause’ commands? Will they eat up minutes from my daily available capacity?
The short answer is ‘Yes’. You may want to review the ‘Pause’ commands in your scripts and adjust their timing down at least if you cannot remove them completely.
But please ensure that you do not have ‘Pauses’ for more than 16 minutes in case you are you are using Worksoft SaaS Cloud as your platform for executions within your domain. Worksoft SaaS will automatically abort the test if a ‘Pause’ command pauses for more than 16 minutes. (If you are familiar with Selenium, the “IDLE_TIMEOUT” set within Worksoft SaaS is 16 minutes.)
If you are using BrowserStack as your execution cloud platform, please note that the “IDLE_TIMEOUT” is 90 seconds, and hence if you use a “Pause” for more than 90 seconds, your tests will abort at 90 seconds.
As much as possible, please use the ‘waitFor’ group of commands instead of explicit pauses.
My test scripts have too many commands from the ‘waitFor’ group of commands? Will they eat up minutes from my daily available capacity?
The short answer is ‘Yes’. But ‘waitFors’ are lot better than explicit ‘Pauses’. We assume that you have a genuine need for these waitFor commands in your scripts.
The only thing we recommend doing in the context of using your available daily capacity is that you may want to review the ‘waitFor’ commands in your scripts and adjust their timing down to values that will still match your application’s performance and/or behavior.