The Automated test runs page shows a list of all active and finished automated test runs that users requested from a given Test Plan using the Run automated tests operation. Thanks to this queuing, you can schedule more than one automated test run within a given Test Plan without having to wait until the first execution is completed. All pending or running automated test runs you can view on the Active tab, and when they are complete, the entries are moved to the Finished tab.
There are two ways to access the Automated test runs page:
To view the automated test runs you need to configure at least one Continuous Integration server and have permissions to browse projects with automated tests. Learn more at Test Automation configuration.
The CI server polling service works as described in the diagram below:
The User uses the Run automated tests operation on Test Plan. Then the automated test run flow can take the following statuses:
TestFLO polls the CI server every 30 seconds, and the Automated tests runs screen needs to be refreshed manually to see the current statuses.
The Active tab shows all active requests of automated test runs. Each test run can take the following statuses: Waiting, Queued, and Running.
To obtain an appropriate range of data you can filter active automated test runs with the following categories: Project, Test Plan, Status, and Job name.
Depending on the current status, you can perform actions on each of the entries by clicking on the three dots icon in the Actions column. Available actions:
Waiting | Queued | Running | |
---|---|---|---|
Jenkins | View job parameters | ||
Bamboo |
The Finished tab shows all finished requests of automated test runs. Each test run can take the following statuses: Passed, Failed, Error, and Canceled.
To obtain an appropriate range of data you can filter finished automated test runs with the following categories: Project, Test Plan, Status, and Job name.
Depending on the status, you can perform actions on each of the entries by clicking on the three dots icon in the Actions column. Available actions:
Passed | Failed | Error | Canceled | |
---|---|---|---|---|
Jenkins | View job parameters | |||
Bamboo | View job parameters |
The number of entries stored in the Finished tab you can manage using the Finished CI job runs retention period (days) option. You can set how many days after the completion of a given automated test run will be stored in the database. By default, entries are stored for 30 days.
For more information see Finished CI job runs retention period (days) in TestFLO Settings.