Skip to content

Triaging in Worksoft SaaS

← Triaging Test Run failures in Worksoft SaaS

Overview


Worksoft SaaS provides multiple features to record test failures. Usage of these features allows for you to not only reduce the time you spend triaging failures but also help manage issues within the system and generate required reports. The following are the different features that come handy during this process.

a) Root Cause for Failures
b) Auto assignment of Root Cause for Failure by Worksoft SaaS using AI/ML
c) Auto re-execution of failed Test Runs
d) Issue Store &
d) Annotations

Root Cause for Failures:


When you create a Project in Worksoft SaaS, a list of labels (you can read more about labels and administration by visiting this article) are created by default. Root label "Root Cause for Failure" and its children are some of the labels that are created as part of this process. As the name suggests "Root Cause for Failure" label is used for doing high-level classification of failures like "Application Defect", "Application Change" etc.

To get the maximum benefit from Worksoft SaaS Analytics you are recommended to make use of "Root Cause for Failure" labels. When you assign test run to this label, counts show up in the Worksoft SaaS Analytics & Dashboard (if you continue to use the default list of reports) as a report.

Auto assignment of Root Cause for Failure by Worksoft SaaS using AI/ML:


This feature in Worksoft SaaS greatly helps you by reducing the time you have to spend categorizing the failures. Worksoft SaaS uses AI/ML to predict the reason for a test run failure and assigns the "Root Cause for Failure" given that these failures are seen in the project at least once and you have assigned the label for the specific test run. As with any AI/ML logic, Worksoft SaaS assigning right "Root Cause for Failure" label depends on the data it is given to train itself and you play a major role by ensuring earlier failures are assigned to the right label.

Refer to the article here for more details.

Auto re-execution of Test Run failures:


Any automation has some amount of flakiness either caused by the inherent technology limitations or owing to the AUT behavior. In such cases, the general practice is to execute these tests more than once to rule out flakiness being the reason for failure. Following this general practice, Worksoft SaaS re-schedules tests that are classified as "Worksoft SaaS Flakiness" or "Application Flakiness" when the batch is executed. This eliminates the time you have to spend re-scheduling/executing these tests once the batch is complete thereby reducing the overall time you have to spend on completing testing.

Refer to the article here for more details.

Annotations:


You have completed debugging a test run failure and would like to share your findings with your team members or would like to record the findings for further review. In such cases, you can use "Annotations" feature for recording/logging these findings and/or comments.

Refer to the article here for more details.


Feedback and Knowledge Base

(thinking…)