Page Comparison

...

More actions (ellipsis) icon allows you to Refresh, Delete execution or export the result to XLSX or PDF.

...

In the bottom section, you will see general information related to your executions. Here’s a brief description on all of them:

1. ID: This is dynamically generated and contains the ID of the execution set (shown in the first image above) and the ID of the selected execution separated by a dot.

2. Started By: This shows the username of the person who started the execution. It may or may not be the same user who created the execution set

3. Started On: This shows the date/time in which the run was triggered (in other words, sent to cloud run, but may not necessarily have started execution yet)

4. Completed On: This shows the date/time in which the execution finished

5. Duration: This shows the duration of the execution

6. Runs: This shows the number of execution runs

7. Reruns: This shows the number of reruns that were either started automatically or manually by the user

8. Type: This shows the type of cloud run request. The value here could be one of 3:

   1. Portal: Started directly by the user (clicking Cloud Run icon)

   2. Scheduled: Started by Subject7 automatically using a schedule defined by the user

   3. Web Service: Started by API (Either directly via the API or by using Jenkins CI/CD plugin)

9. Pool: This shows you the pool configured in the execution set where execution took place

10. Browsers: This shows you which browser(s) you configured in the execution set. The greyed out ones have not been select in the below image.

...

In the last section of the detail pane, you will see your Test Runs separated into 2 categories: All and Failed. Since the user will mostly be concerned with checking the failures, the Failed view will be activated by default, but you can click All to see all of the executions.

...

The link under Test Case column will navigate to a different screen that will show you a more detailed view of your executions.

...