One of the common use cases that you may have been experiencing is your development team or your business users asking you to get a specific subset of tests from your regression test suite to be re-executed. Such requests usually get made when specific issues get resolved or when some changes have been done to functionality within a specific set of application modules/components.

So far, you or your peers had to put in some manual effort to create data files for the driver to just include the testing context keys that have to be executed along with other inputs (business data file overrides, user-define variable overrides, etc, if any).

This release provides you a more efficient approach. The QaCONNECT REST API service (https://www.eureqatest.com/rest/v1/:domainname/executions - POST) has been enhanced to let you specify a configuration that will let Worksoft SaaS know your preferences for the tests to be re-executed. This can be done by passing a value into a new input parameter that has been added to to the service with the name "ConfigurationForAutoScopeDeterminationAndTestExecution". So far, you had to pass as mandatory input to this REST call, the list of tests (testing context keys) you want to execute or re-execute. With the new enhancement, instead of specifying the list of testing context keys you can pass the configuration that will let Worksoft SaaS determine the tests to be re-executed.

It is important for you to note that the tests that get (re-)executed will use the same data used (bound) to the tests being re-executed.

The configuration may include a combination of inputs. These inputs include:

• testCycleList:Specific test cycle(s) within which the test runs that should be re-executed are part of. If you don’t specify the parameter, the tests that failed within the TestCycleIdentifier parameter in this REST API request will be used (meaning the re-executed tests will be run in the same test cycle that the tests that needs to be re-executed are part of). If values are provided, a full test cycle identifier must be provided. If there is more than one test cycle, a comma separated list has to be provided (example: "Smoke_Cycle_Oct_11, Smoke_Cycle_Oct_12”).


• onlyOriginallyScheduledTestsIndicator:Whether only the originally scheduled runs in the test cycles should be considered for re-execution. By default, this parameter is set to false, meaning the originally scheduled tests, the tests auto re-executed by Worksoft SaaS ML as well as the manually re-executed tests will be considered.


• onlyReportableTestsIndicator: Whether or not only the reportable runs in the test cycles specified above must be considered for re-execution. If you don’t specify this parameter, only reportable runs are considered.


• testRunStatusList: Specific execution statuses with which the test runs that needed to be re-executed ended with. If you don’t pass a value to this parameter, Worksoft SaaS will consider all statuses. If you pass a value, it must be a comma-separated list of status names. Example: "Completed w/ failures", "System Aborted", "Aborted".


• firstPointOfFailureErrorDescriptionList: The value passed into this parameter represents the one or more comma-separated list of specific error descriptions for the first failed Instruction for the runs that you want re-executed.  Example: "my error text 1", "my error text 2"). 


• labelsAssignedToTestsList: The value passed into this parameter represents the specific labels attached to the test runs that need to be re-executed. This is optional. If you pass more than one label as part of the value, it must be a comma-separated list of labels (example: For application modules use case, you can pass something like "Shopping Cart", "Product Detail Page").


• IssueStoreForTheIssuesLinkedoTestsList: This is the issue store that has the issues listed in the next parameter. It can be one of the following values: "Local" or "External-Jira". If you don't specify a value, "Local" is assumed.


• IssuesLinkedoTestsList: The value passed into this parameter represents the specific issues in the local issue store (or external issue tracking system (like Jira) linked to the test runs that you want re-executed. Input value for this parameter is conditionally required. If you pass a value for the above parameter, then you must pass a value into this parameter. If you specified "Local" for the "IssueStoreForTheIssuesLinkedoTestsList" parameter, then you are expected to pass as value into this field a comma-separated list of local issue store keys. If you specified "External-Jira" for the "IssueStoreForTheIssuesLinkedoTestsList" parameter, then you are expected to pass as value into this field a comma-separated list of JIRA issue keys.

A few useful examples have been added in the QaCONNECT REST API DOCS page for this service that will help you easily understand how you can use this feature.

In addition, a new QaCONNECT service: https://www.eureqatest.com/rest/v1/:domainname/executions/query has been added to the QaCONNECT REST API and listed in the DOCS page) that will allow you to verify if the values you intend to pass into “ConfigurationForAutoScopeDeterminationAndTestExecution" parameter of the service (https://www.eureqatest.com/rest/v1/:domainname/executions) correctly yields the specific tests that you are interested in getting re-executed (and nothing more or less).

It is strongly recommended that you first call this service with the values you intend to pass into the parameter “ConfigurationForAutoScopeDeterminationAndTestExecution”, get the results, verify that the tests that you get back as a response from this service exactly matches your expectations before you pass the same parameter into the Scheduling service.

Please note that you can request the response, the test run list, to come back as a JSON or a CSV.