Lesson 17 Topic 2 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 17 :: Topic 2
1. Root Cause for Failure Labels
When you create a Project in Worksoft SaaS, a list of labels is created by default. "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 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.
Based on the past history of the Labels assignment made by you to the failed tests in the application, Worksoft SaaS can assign the "Root Cause for Failure"(RCF) labels automatically to the similar failed tests using AI/ML which will reduce the effort of debugging and assigning labels to the failed tests manually.
Worksoft SaaS assigns RCF label to a failed test run in following conditions:
- A test run has failed i.e. one or more instructions in the test run fails
- A test run is executed in the context of a Test Cycle &
- When a similar test run failure is seen in the same Project at least once in the past and you have assigned a label (Root Cause for Failure) to the test run
- You may notice that not all failed test runs have RCF assigned by the system. The reason can be to do with that the failure is new in the Project and/or the confidence factor is less than 50%.