The Automation Queue section displays all the requests created in the queue or the requests executed in the past, regardless of whether they were started manually by playing a Test run or through a schedule. You can set multiple schedules or start Test runs manually on the rTesters; the requests will be queued in waiting status and they will be executed in sequential order.
The requests can have the following statuses:
- Waiting: The request is queued to execute the assigned schedule or Test run on rTesters.
- Running: The request is executing the assigned schedule or Test run on rTesters.
- Completed: The request has been executed successfully and it is finished.
- Completed with Warnings: The request has finished the execution with warnings.
For instance, if you stop a Test run (which was in a queue) manually, then the request will finish the execution with warnings.
- Completed with Errors: An error interrupted the execution of the request.
For instance, if a rTester goes offline while executing a request, the request will be finished with errors.
- Stopped: A request has been stopped by clicking the “Stop” button before it finished the execution. This is only available when the request is in “Running” status.
Displaying a Test run or a schedule of request
To view more information about all requests, click the request name. If the request was created by a schedule, you will see the schedule details.
If it was created by playing a Test run manually then you will see the Test run details.
Additionally, you can view the request logs by clicking request ID. The log window is displayed and enables you to view log messages for it. This will help you with troubleshooting the ones with errors or warnings.
You can delete a scheduled request from the queue by clicking “Delete” button.
You cannot delete a request that is in “Running” status but you may stop it.
Note: If you set multiple schedules on the same rTester and their execution time overlaps, the requests are queued, in a waiting status. The rTester executes the queued requests in sequential order.
Note: If the rTester is offline for any reason, the schedules that were supposed to be run at that point are completed with errors.
Note: If the rTesters are busy or reserved, the requests will execute the schedules or test runs as soon as the rTesters become available.