Test Report Generation Using Business Activity Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for showing test results in software testing projects, particularly for user acceptance testing, are limited in effectively presenting business activity results and statuses, leading to inefficiencies in test planning and management.
Innovation Solution
A system and method for generating test reports that involve identifying testing projects, creating diagrams of test flows with multiple scenarios, extracting relevant scenarios, generating an executable test list with linked activities, and producing reports that display execution results, including execution rate, pass rate, and activity status, using either historical or current project data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional test result presentation methods are used, then the testing process is simpler, but the ability to effectively present business activity results and statuses is limited
Solution Approach 1:
The patent segments test results by business activities, organizing test cases and outcomes according to specific business processes rather than traditional test hierarchies. This segmentation allows stakeholders to view test results in the context of specific business activities, preserving information about how testing impacts actual business operations while maintaining manageable report structures.
Solution Approach 2:
The patent introduces a new dimension to test reporting by adding business activity context to traditional test results. Instead of only showing pass/fail rates, the system displays results organized around business processes, timelines, and operational impacts, creating a multi-dimensional view that preserves critical business context without requiring excessive system complexity.
2Reliability
If comprehensive test results are presented, then decision-making is improved, but the complexity of test planning and management increases
Solution Approach 1:
The patent extracts and highlights only the most critical test results and business activity statuses needed for decision-making. Rather than presenting all available test data, the system identifies and displays key metrics such as pass/fail rates for critical business activities, timeline adherence, and high-impact defects, improving decision reliability while reducing planning complexity through selective information extraction.
Solution Approach 2:
The patent applies local quality by providing different levels of detail for different business activities based on their criticality. High-priority business activities receive detailed tracking and reporting, while lower-priority activities receive summarized views. This differentiated approach enhances decision-making for critical areas without increasing overall management complexity across the entire test program.
3Productivity
If test results are aggregated at business activity level, then efficiency is enhanced, but the level of detail may be reduced
Solution Approach 1:
The patent implements dynamic reporting that adapts the level of aggregation based on user needs and context. The system can dynamically switch between aggregated business activity views for high-level efficiency monitoring and detailed test case views when specific issues require investigation. This dynamic adjustment allows the same system to enhance efficiency through aggregation while preserving access to detailed measurements when needed.
Solution Approach 2:
The patent uses a nested structure where business activity-level aggregations contain and can expand to reveal individual test case details. Each business activity summary is nested with the ability to drill down into constituent test cases, maintaining both the efficiency benefits of aggregation and the precision of detailed measurements through a hierarchical, expandable report structure.
Data Source
AI summary
A system, method, and computer program product are provided. At least one testing project to be performed is identified, and a diagram is generated from testing activities including parameters with multiple values which includes one or more test flows including the testing activities. The one or more test flows include a plurality of possible testing scenarios. Further, scenarios are extracted from the generated diagram, and a test list to be executed is generated utilizing the extracted scenarios where each test case in the test list retains a link to a corresponding testing activity in the generated diagram. Still yet, the test list is, and at least one report is generated based on the execution of the test list which shows the generated diagram and a result of the execution corresponding to a testing activity based on an associated retained link.