Skip to content

Lesson 17 Topic 1 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 1


1. Worksoft SaaS Analytics
Worksoft SaaS Analytics provides you with a strong and rich reporting structure. This plays an important role for you to understand the application behavior while performing tests on cross-browser and cross-device. It also helps you plan the capacity and subscription of Worksoft SaaS.

If your user account is configured as 'Customer User', you have access to 3 categories of reports in each of the Project you are authorised for. These are
  • Quality - "Quality" reports give you an in-depth understanding of the Test Runs executed
  • Planning - This report will help you plan the Test Executions
  • Subscription Usage - This report will help you with insights into how you are utilizing the 'capacity' and 'concurrency' from your Worksoft SaaS Subscription
If you are an admin in Worksoft SaaS, you also get to see Quality & Subscription Usage reports across all Projects in your domain under "Administration" context.

Worksoft SaaS presents these reports in two views: Tree & Dashboard. Under Tree View all reports are show under corresponding accordion while Dashboard provides a quick view of Test Cycle Level Outcome Reports only.

2. Test Cycle Level Outcome reports
The 'Test Cycle based Test Outcomes' set of reports under 'Quality' which provide rich analytics in the context of specific Test Cycles.

This report will help you visualize/understand how the test outcomes vary by application release/iterations (test cycles) across numerous dimensions like project environment, product flavor, browser/operating system platform, etc.,

These rich analytics can be accessed in various ways across numerous dimensions:
  • At Project Environment
  • At a Test Cycle Level By Run Definition
  • By Browser / Operating System Platforms By Application Module and By Run Definition
3. Test Cycle Consolidated Triage Report
This report helps automation developer to start the troubleshooting process, it gives a clear picture of how many tests have failed and why they have failed . This report also helps you with insights about the issues created/linked during the executions of the tests that are part of the Test Cycle which you can you to start the troubleshooting process. 

This report will also give you the information about how the 'capacity' is being utilized for the tests which are auto re-executed using the Worksoft AI/ML feature.

4. Test Cycle Outcomes and Triage Comparison Reports
This report will allow you to compare the test outcomes and the triage details of up to 4 test cycles within your project.

5. Project Level Test Outcomes by Time Period

These rich analytics can be accessed in various ways across numerous dimensions:

  • At Company (Account-level), Project and User levels
  • At a Test Cycle by using Test Cycle Identifier (however your builds are identified)
  • For a specific Calendar Time Period
  • For a specific Testing Purpose (Smoke, Regression, etc)
6. Test Cycle Clipboard Consolidation Reports
This report provides insight on Test Data used in testing, this will also help in the process of troubleshooting.



Feedback and Knowledge Base