Worksoft SaaS performs the auto-triage for the failed tests within a test cycle. The main purpose of this QaCONNECT Service is to perform the auto-corrections of the Root Cause for Failure labels and the issues that are assigned to the test runs that are executed as part of a test cycle. This way, you are going to save a lot of time.

You can simply execute this service to perform the corrections for the tests that are triaged within a test cycle. This service is available in the QaCONNECT REST API Docs page under the Test Cycles Section.

Attributes that are available for this service are:

• sourceTestCycles(Mandatory): You need to specify the Test Cycle Identifier(s) for which any of the assignments (Root Cause for Failures/linking/delinking of the issues) has happened.
• targetTestCycles(Mandatory): Under this section, you need to specify the Test Cycle Identifier(s) for which the root cause for failure labels/issues of the test runs are to be updated.
• scopeOfAutoCorrection(Mandatory): This parameter determines whether you want to perform the actions for only Root Cause for Failure labels or only Issue Linkages or to all of them. When you specify as “00”, it applies to both, and on specifying “01” will limit to Root Cause for Failure labels only and on specifying “02”, it will limit to Issue Linkages only.
• conditionsForAutoCorrection(Mandatory): This is the parameter that defines how the auto corrections are to be made for the test runs. Accepted values for this parameter are:
  • 01- On specifying this value, you are performing the auto-correction for the test runs which are not yet assigned by any of the Root Cause for Failures or linking of the issues either manually or by Worksoft AI/ML.
    For example, you have a specific use case of auto-correction for the test runs which are not assigned with any of the RCF or issues in the Target Test Cycle, then you can specify this value as “01” in the “conditionsForAutoCorrection” parameter.
  • 02- On specifying this value, you are performing the auto-correction for the test runs which are assigned by any of the Root Cause for Failures or linking of the issues by Worksoft AI/ML and are not done manually by you or your team members.
    If you choose this option, any Test Runs where you or your team members explicitly assigned/corrected root cause for failures and/or issue linkages manually will be ignored from auto-correction.
    For example, you have a specific use case of auto-correction for the test runs which are assigned with any of the RCF or issues in the Target Test Cycle by Worksoft AI/ML, then you can specify this value as “02” in the “conditionsForAutoCorrection” parameter.
  • 03- On specifying this value, the auto-correction happens for the test runs which are either assigned by Worksoft AI/ML or by the users that have performed actions(assignment of RCF labels/Issue linkages) to the test runs in the Source Test Cycle along with the test runs for which no root cause for failures and issues are assigned.
  • 04- On specifying this value, you can perform the auto-correction for the test runs which are either assigned by euerQa AI/ML or by the users that have by the users that have performed actions(assignment of RCF labels/Issue linkages) to the test runs in the Target Test Cycle along with the test runs for which no root cause for failures and issues are assigned.
• usersThatPerformedActionsInSourceTestCycles(Optional): In this parameter, you need to specify the user names whose changes made to the test runs in the source test cycle are to be reflected in the target test cycle. For example, you are working with your team members for a project and all or a few of you have made changes and you want to see only specific user’s changes, then you need to specify that username in this parameter. If you don’t specify any user name, it would take the username of the user to give the service request.
• usersThatAssignedRootCausesInTargetTestCycles(Optional): For this parameter, you need to specify the usernames of a specific user(s) that assigned root cause of failures for runs or linked/delinked Issues to/from runs within the targetTestCycles that the updates as a result of this request should be restricted to. If you don't explicitly specify, it defaults to all users including the user that made the call to this service.
• conditionAutoCorrectionMatchAccuracy (Optional): You need to specify the accuracy percentage for performing the auto-corrections, unless there is a match of the mentioned percentage(%) between the criteria used by the Worksoft AI/ML engine between source and target, the data from the source test cycle will not be used to correct data in the target test cycle. You can override the default with any value between 0 to 100. For example, if you want to only get the corrections made when there is a 100 percentage(%) match, you can pass a value of 100. If you want corrections made even when match accuracy is say 70 percent(%), then you should pass 70 as value to this parameter.
• conditionCutOffDateTimeForSourceUsersThatPerformedActions(Optional): Using this parameter, you can specify the specific user’s DateTime who performed the actions like the assignment of the root cause of failures or linking/delinking of the issues to the test runs. The changes made from that DateTime will be taken into consideration for the auto-corrections of the test runs in the target test cycle.
  For example, you have made multiple changes within a day to the test runs in the source test cycle and now, you wish to have only the latest changes to be reflected in the target test cycle, then you can give that specific DateTime as the value to this parameter, then only actions performed on or after that date-time passed as the value will be considered.
  The default cut off DateTime will be the date-time of the first actions performed by the source users within the source test cycle(s). This parameter will come handy if you want only the latest actions to be considered.
  The valid format which this parameter accepts is 'MMM DD YYYY HH:MM'. In this format hours and minutes are optional.

To know more about this service in detail, refer to the QaCONNECT REST API Docs page.

Few use cases using the Auto Triage Correction Service are available here.