The main purpose of this feature is to reduce the failures and increase productivity by performing the sanity check(s) wherever needed before going into complete regression tests. As a result, you can save

• Capacity: By finding the root cause of the failures occurred in the scheduled runs by performing a sample check instead of triggering all the test runs at a time.
• Prioritization: You can prioritize the execution of test runs according to your usage.

You can now trigger the test runs via QaCONNECT by specifying a few additional parameters which will now allow setting the priority and dependency for the test runs.

The new parameters that are to be included in the executions call service (https://www.web.worksoft.cloud/rest/v1/:domainname/executions) are:

• batchConfig: This parameter allows to group different conditions for a Batch w.r.t Batch Label
• batchLabel: This parameter allows to group different run definition testing context keys under one batch.
  For example, you want to execute the basic tests as part of Sanity Tests or Regression Test Suite, you can use this batch label. You can also filter the tests executed based on the 'batchLabel' in the Test Runs Home screen using the 'Batch Label' field in the Basic Search Criteria.
• waitTimeForAutoCancelling: This parameter allows you to specify the wait time for auto canceling of the dependent runs. Accepts numeric value in hours. Defaults to 16 hours if you do not pass a value into this parameter
• triggerConditionsForTheBatch: This parameter allows to specify various trigger conditions w.r.t batch. You can specify a condition like Batch1 should only trigger only if one of the run definition testing context keys is completed
  
• testCycleIdentifier: The Test cycle identifier on which the executions are dependent
• runDefinitionTestingContextKeys: The run definition testing context keys on which the current executions are dependent
• testExecutionStatusList: The different statuses on which the executions are dependent on
  01 - Completed w/o Failures
  02 - Completed w/ Failures
  03 - Aborted
  04 - System Aborted
  05 - Cancelled
  06 - All of the above
• delayPreprocessingIndicator: This parameter allows to delay the preprocessing for all the runs part of the dependent batch. This parameter accepts 'true' or 'false' as values with the latter being the default.

Mandatory parameters that are required in the batchConfig JSON:

• testExecutionStatusList

• When 'batchLabel' is defined in the 'triggerConditionsForTheBatch' JSON, then the 'testCycleIdentifier' should be mandatory in the same JSON

For the test runs which are not yet moved to 'Scheduled/In-Progress' state, because of the priority/dependency is shown with the dependency icon in both the Test Runs Home and Execution Results tabs as shown below:

When you click on this icon, a popup will display the test cycle, run definition testing context keys and batch label information where you can copy the test cycle identifier by clicking on the 'Copy to Clipboard' icon. If there are any dependent testing context keys in the JSON, they will be shown under the 'Testing Context Key(s)' column and those can be copied by performing a click on them.