Skip to content

Quality Reports :: Before you Generate Test Cycle Level Test Outcomes

← Worksoft SaaS Analytics : Reports & Dashboards

Before you read this you may want to see:

Test Cycle Level Test Outcomes

The 'Test Cycle based Test Outcomes' set of reports will provide rich analytics about the Quality Assurance initiatives in the context of specific Test Cycles.

Using reports under this category will give you a greater understanding of how quality assurance efforts are operating and to what extent they are actually succeeding within your project(s), using Test Cycles as the key dimension.

To generate these reports, there are prerequisites that need to be defined and that would help you achieve the desired output.

Prerequisites:

  1. Worksoft SaaS Analytics Configuration
  2. Create Labels based on Application Modules
  3. Mapping Labels to Test Artifacts - Test Scripts and Run Definitions
  4. Execute the Test Runs with Test Cycle Identifier
  5. Generate Customized Reports
  6. Customize Data in the Transactions Detail Report

1. Worksoft SaaS Analytics Configuration

These reports 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.

Worksoft SaaS domain admin can customize the hierarchy of the reports to be generated at Analytics Page. Report hierarchy enables the team to view execution results in multiple directions based on project requirement. This customization of reports is highly recommended to complete during the Project setup in Worksoft SaaS. Admin can also change the reporting hierarchy anytime during the project progress under “Projects” > “Worksoft SaaS Analytics Configuration”.If the hierarchy is not mentioned there is a default hierarchy set by Worksoft SaaS.

This rich analytics can be accessed in various ways across numerous dimensions.

2. Create Labels: Application Modules

After completing the configuration of the hierarchy of reports. Create Child Label(s) to System Created Label - Application Modules. 

You may create all the modules that are available within your application as child labels.

3.   Mapping Labels to Test Artifacts - Test Scripts and Run Definitions 

Upload the Test Scripts and map child level modules, of the – Application Module. For Performance Testing, it is mandatory to map artifacts that are functional to labels 

Automation Entity Purpose/Performance Report Mapping-

  • Test Scripts to Usage Step
  • Run Definitions to Business Workflow.
Test scripts that are mapped to ‘Usage Step’ label are the ones that appear in a report. For Functional/Regression Testing it is not mandatory to map to these labels.

4. Customize Data in the Transactions Detail Report  

Refer to the QaCONNECT REST API Docs on how to configure the custom template. To know more, click here.

5. Execute the Test Runs with Test Cycle Identifier 


Refer to the QaCONNECT REST API docs on how to create a Test Cycle and Execute the Test Runs using Test Cycle Identifier.

6. Generate Customized Reports   

Navigate to Analytics home page and generate customized Reports based on the Test Cycle Identifier provided during the execution of the Test Cycle Level Test Outcomes under Quality.

Click here to know and understand the generated reports.


After you read this article you may want to see:

Feedback and Knowledge Base

(thinking…)