Skip to content

Worksoft SaaS Analytics Configuration

← Administration: Projects & Products

Before you read this you may want to see:

Main Article


The 'Analytics Configuration' allows you to set up the hierarchy that is needed for your 'Test Cycle Level Test Outcomes Reports' which gives you the metrics of the executed test runs. You can set the default hierarchy according to your requirements and business needs.

For example, if you want to generate reports based on the run definition, you specify that entity as the parent in the hierarchy.

You can customize Worksoft SaaS Analytics Reports based on your reporting needs within the Project. The customization impacts the "Test Cycle Level Test Outcomes" reports in the Analytics module.

Worksoft SaaS Analytics Configuration allows you to customize Function/Regression Testing and y ou have to be an 'Administrator' to be able to configure Worksoft SaaS Analytics within a Project.

While creating a project or editing a project, navigate to the Worksoft SaaS Analytics Configuration section. A drop-down to select the Function/Regression Testing is available.

Functional/Regression Testing: 
If you do not customize the reporting hierarchy in a project, Worksoft SaaS automatically applies the following as the 'default' hierarchy. You can change the configuration for your hierarchy any time you choose to modify it.


A template to configure the hierarchy opens which is a tree structure. For Functional/Regression Testing, the Test Cycle Level Test Outcomes depends on the hierarchy configured.

The entities that can be configured are Environment, Run Definition, Test  Cycles, Application Modules, Labels, and Testing Platforms.

The maximum root nodes that can be created is 3. The maximum depth of the root node is 6 and for each root node, maximum child nodes allowed is 3.

Below are the steps to create the Root Nodes and Child Nodes in the Analytics Hierarchy Configuration.
  1. Click on the first icon to create the root node. Once a value is selected, the value cannot be part of the root node or child node.
  2. Click on the  second icon to create the child node.
  3. The third icon deletes the selected node. 
    4. Note. The default value selected cannot be changed.
  4. After configuring, you can click on 'Save & Preview' if you wish to see the hierarchy before generating the reports or click on 'Save & Close' which closes the popup with the changes reflected in the hierarchy.
By default, once you add the root nodes and child nodes, you can see the checkboxes for 'Generate Summary' for all the nodes and 'Transactional Detail' only for 'Test Cycle' entity. Upon selection, you can see those reports generated for the entities in the 'Test Cycle Level Test Outcomes Reports'.

On selecting the nodes as any of the labels, you can see two selections available
  1. Select Entity: This will help you in generating the reports for which the labels are tagged to the respective entity ( Run Definition/Scenario/ Test Script)
  2. Label Levels: This indicates the levels of the labels and the level which has to be considered while generating reports.
By default, the 'System Labels' are supported up to 3 levels and 'User-Defined Labels' are supported up to 5 levels. So, when you select any system label(s), you can '2, 3' values in the dropdown and for the user-defined label(s), you can see '2, 3, 4, 5' values in the dropdown.

Below are the steps to Configure Hierarchy:
  1. Click Project drop-down and select Administration
  2. Select Projects from the Menu icon
  3. Edit the project
  4. Select Reports Category in Worksoft SaaS Analytics Configuration page
  5. Configure the Hierarchy
  6. Click on Save & Exit
You can see the updated hierarchy below along with the selection of the entities and label levels.



'Test Cycle Level Test Outcomes' reports will be generated with the hierarchy configured in the 'Analytics Configuration'. While Worksoft SaaS allows you to choose hierarchy based on above rules, you would like to make a note of one subtle difference between hierarchy defined with Test Cycle as the root versus other options.

Generating Test Cycle Outcomes Reports for more than one Test Cycle simultaneously

Worksoft SaaS platform is designed to be flexible to cater to the needs of its users. One such requirement is that system allows for generating test cycle outcomes reports for multiple test cycles simultaneously. Especially when each environment has different test cycles executed, it allows for no summaries to go across. In such case you can define Test Cycle as the root and system would allow for generating reports for test cycles simultaneously.

While the system allows for triggering of test outcome reports for multiple test cycles at the same time, in other hierarchies only one report is moved in "In Progress" state while others are retained in "Queued" state. And system will pick up one test cycle at a time and generate reports in random fashion.




Feedback and Knowledge Base

(thinking…)