Skip to content

Drill-down/View into Tests that ran within a Test Cycle

← Managing Test Cycles


Before you read this you may want to see:

Main Article


From time to time,  you will experience the need to view the automated tests that are included in a Test Cycle. Sometimes this need may arise when you are executing tests within a cycle (for you to check of the tests are proceeding well) and some other times, a need may arise after all the automated tests within the cycle have completed execution ( and you just want to view the outcomes of individual tests.)

Worksoft SaaS offers multiple mechanisms for you to access the list of automated tests within a test cycle.
  • You can use "Test Runs column" on the Test Cycles' home screen to drill down to the list of tests in a specific status
  • You can search/filter the Test Runs' home screen on 'Test Cycle Identifier'
  • You can retrieve the list of tests using QaCONNECT REST API
  • You can copy the Test Cycle Identifier by using the "Copy to Clipboard Icon"

Drill-down to Automated Tests from Test Cycles' home screen


Follow the instructions provided below to view the listing of automated tests (aka Test Runs) within a Test Cycle by the status of the tests, and to drill-down to the details of the test execution. 

When on the 'Test Cycles' home screen, click on the graphical icons in the last column "Test Runs". 

                                  

Click on the top right-hand side of the screen to see the legend for the icons.  
You will see the icons are named after the status of the automated tests within each Cycle listed on the screen.
Each icon (Queued, Preprocessing In-Progress, Preprocessing Completed, Preprocessing Failed, Preprocessing Cancelled, Scheduled, In-Progress, Aborted and Completed) will summarize for each cycle, the count of automated runs within the given cycle in a specific execution status.

To view the list of Test Runs in a specific status, click on the hyperlinked count displayed in the appropriate status icon for the specific Test Cycle of interest to you. This action will take you to the Test Runs' home screen and auto-filter and show you the test runs in the specific status for the specific Test Cycle. From there, you can click on the 'hyperlinked' status column to access/drill-down to the execution detail of individual test runs.

Search/Filter the Test Runs' home screen by Test Cycle Identifier

An alternate mechanism for you to get a list of automated test runs within a test cycle is to go to the Test Runs' home screen, expand the search/filters (using the 'magnifying glass icon' on the top right hand side of the screen), key in the 'Test Cycle Identifier' of interest to you and initiate a search.

This action will show you the test runs for the specific Test Cycle. From there, you can click on the 'hyperlinked' status column to access/drill-down to the execution detail of individual test runs.

How can I access/view the Test Cycle within which my Test Run was executed?

If your not sure which Test Cycle a particular automated test run was executed within, don't worry. There are two easy ways for you to get to the Test Cycle.

1. You can get the detail from the Execution Detail screen of a specific Test Run. 

The Test Cycle icon is shown just before the Test Run ID on the Execute tab of a Test Run.

Mousing over on the icon will give you the details about the Test Cycle:

  • Test Cycle Identifier
  • Status of the Test Cycle (Open or Closed)
  • Description of the Test Cycle, if available
  • Planned Window Time
  • Actual Window Time
  • UserNotes (If any)
  • User that assigned the Test Run to the cycle
  • Datetime when such an assignment/linkage was done
2. Alternatively, you can also get the details of the Test Cycle that a Test Run belongs to (or executed within) from the Test Runs' home screen.

Among other important details related to the test run, mousing over on the 'Test Run Key' will give you visibility into the Test Cycle. If you want to, you can also copy the Test Cycle Identifier after hovering on the Run Definition Key, and use it elsewhere (say in searching/filtering test runs based on the Test Cycle Identifier)

After you read this article you may want to see:

Feedback and Knowledge Base

(thinking…)