Skip to content

Linking Automated Tests to a Test Cycle

← Managing Test Cycles


Before you read this you may want to see:

Main Article


Any number of Automated Tests can be executed within a specific Test Cycle. Worksoft SaaS does NOT impose any restrictions on the number of tests that can get executed within a test cycle.

A test run belongs at most to a single Test Cycle. A test run does NOT have to belong to any Test Cycle. If you want to execute automated tests without including it in any test cycle, you can do that as well.

At any given point of time, you can have more than one Test Cycle in the 'Open' state. In other words, you can concurrently have automated tests running in more than one Test Cycle if your project demands it.

Linking Automated Tests to a Test Cycle 

Test runs can be linked to Test Cycle in two ways:

1. At-Scheduling-Time-Linkage: At the time of scheduling a Test by using QaCONNECT REST API
                                                     
                                                                                                              

When you schedule/trigger the execution of one or more Run Definition(s) using QaCONNECT REST API, if you intend to associate/link those test runs to a particular Test Cycle, you must pass the "Test Cycle Identifier" of the Test Cycle of your interest, as one of the inputs to the QaCONNECT REST call. It is that simple!

How to schedule a batch of test runs linking a Test Cycle: To schedule a batch of test runs within a test cycle, follow the below steps.

  1. You must have the list of Testing Context Keys of the Test Runs to be scheduled within the specific Test Cycle.
    To know more about the Testing Context Keys, click here.
  2. Once you are ready with the testing context keys, you need to prepare the JSON with the below-mentioned request URL.
    https://www.web.worksoft.cloud/rest/v1/:domainname/executions
    {
      "TestCycleIdentifier": "Your Test Cycle Identifier",
      "RunDefinitionTestingContextKeys": [
        {
          "id": "RUN_DEF_TESTING_CONTEXT_KEY_01",
          "status": "YOUR_RUN_DEF_STATUS",
          "userNotes": "SOME_DESCRIPTION"
        },
        {
          "id": "RUN_DEF_TESTING_CONTEXT_KEY_N",
          "status": "YOUR_RUN_DEF_STATUS",
          "userNotes": "SOME_DESCRIPTION"
        }
      ]
    }
  3. In the JSON, the required parameters such as 'Test Cycle Identifier', 'Run Definition Testing Context Keys' along with 'Status(Mandatory)' and 'User Notes(Optional)' should be provided.
  4. Once, the JSON is ready, you can trigger the 'POST' service using the request URL either using wsCONNECT Commands or using any of the external tools. 
2.Post-Scheduling Linkage:  Within Worksoft SaaS application, from the Test Run's "Execution Details" screen
                   
                                                       
While this is not a recommended/best-practice approach, Worksoft SaaS allows you to associate/link a test run that is Scheduled, Queued, In-Progress, Aborted, or Completed with a currently 'open' Test Cycle(s).

For instructions on how to assign test runs to test cycles from Worksoft SaaS Saas click here.

After you read this article you may want to see:

Feedback and Knowledge Base

(thinking…)