Test Cycle Level Outcome reports
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.
Mapping the Worksoft SaaS feature to the Course Context :: Lesson 17:: Topic 1
1. Test Cycle Level Outcome reports
When the Test Cycle is created, the Test Cycle Level Outcome reports are automatically generated.
2. Practice
Generation of 'Test Cycle Level Test Outcomes' reports
- Navigate to Analytics screen
- Click on toggle icon available beside 'Test Cycle Level Test Outcomes'
- Click on Customise Report(s) link
- Enter required Test Cycle Identifier name in the Test Cycle Identifier drop-down
- Click on required TCI
- Click on Generate Report button
- Test Cycle Level Test Outcomes reports along with Transactions Detail Report and Consolidated Triage Report will be generated.
Once the reports are generated based on the Test Cycle Identifier, you can drill down and view the results for the particular environment, by:
Run Definition: By Run Definition gives the results at Test Cycle Level and also the list of all the Run Definitions that are mapped to the Business Workflow label.Drilling down by Test Cycle level will give you information on:
- Test Outcomes by Run Definition - This explains the Number of Test Runs executed for each Run Definition and their status - Pass/Fail
- Note: System Aborted Runs are not shown in this report
- Test Failures by Root Cause- This explains the failure reason in your tests to help you prioritize the module or plan the necessary steps to be taken to fix the failure. (This is visible only if the Root Cause for failure label is mapped to failed Test Run before generating the Customized Reports.)
- Test Execution Times - Show the execution time of the Run Definition in seconds. This also shows you the outliers in the executions.
Impact on Outcome - By Application Module - For the specific Run Definition, mapped to different Application Modules, it gives the data on the pass and failure on the module. This helps in drilling down to the module directly once the failure is identified and fix the issue.
Transaction Details Report: Next to the Test Cycle Identifier name, there is a report called Transaction Detailed report which gives you the detailed report of your test runs. This is an excel sheet and upon clicking on it, it will get downloaded to your local machine. This sheet will have 3 default sheets:
- Test_Cycle_Summary: This sheet consists of summary details of the Test Cycle like Total Runs in Test Cycle, number of Test Runs Passed, number of Test Runs failed, Test Cycle Execution Time, Test Cycle Window Duration etc.
- Test_Cycle_Transaction_Log: This report lists test outcomes and test execution times by run definition. For each run definition, key information about the testing context and labels assigned is also included.
- Failed_Instruction_Log: This report lists all test instructions that failed during execution within the test scripts of the run definitions executed as part of this test cycle.