Test Case Result Propagation in Quality Assurance Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current quality assurance methods for testing applications are inefficient, particularly when dealing with large numbers of test cases, as they require extensive manual updating of test steps, leading to increased time and resource consumption, and inaccurate reporting due to the 'no run' status in fast run methods.
Innovation Solution
A quality assurance application that allows users to mark a test case as pass or fail, automatically propagating the status to all steps, reducing the need for individual step updates and enabling reason entry, while also identifying failed steps in case of a fail indication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the fast run method is used to mark test cases as pass or fail, then the testing speed is improved, but the reporting accuracy deteriorates because test steps remain with 'no run' status
Solution Approach 1:
The patent segments the test case result propagation into two distinct modes: fast run mode that propagates only pass/fail status at the test case level, and normal run mode that propagates detailed step-level results. This segmentation allows users to choose the appropriate level of detail based on their needs, resolving the contradiction between speed and accuracy.
Solution Approach 2:
The system dynamically adjusts the propagation behavior based on the selected run mode. In fast run mode, only high-level test case results are propagated quickly. In normal run mode, the system performs comprehensive step-level propagation. This dynamic adaptation allows the system to optimize between speed and accuracy depending on the specific testing scenario.
2Measurement precision
If the normal run method is used to mark each test step individually, then the reporting accuracy is improved, but the time consumption deteriorates due to the large number of steps to update
Solution Approach 1:
The patent implements partial action by allowing users to select whether to propagate results at the full step level or only at the test case level. When full propagation is selected, the system performs the complete action of updating all steps. When fast propagation is selected, only the essential test case level update is performed. This partial action approach allows users to balance accuracy requirements against time constraints.
3Loss of information
If individual test steps are updated manually, then the detail information is improved, but the ease of operation deteriorates due to the repetitive nature of updating 50,000 steps
Solution Approach 1:
The patent merges the update operation for all test steps into a single bulk propagation action. Instead of requiring users to update each of the 50,000 steps individually, the system provides a unified propagation mechanism that can update all steps in one operation. This merging dramatically improves ease of operation while preserving the option to capture detailed information when needed.
Solution Approach 2:
The system performs the repetitive update task automatically through bulk propagation, eliminating the need for manual step-by-step updates. The propagation mechanism serves itself by automatically distributing test case results to all associated steps, reducing manual effort from updating 50,000 individual steps to a single automated operation.
Data Source
AI summary
A test case for the application under test is determined for the quality assurance application where results for a test case can be received from a user. An interface is displayed to allow the user to enter a pass or fail indication for a manual test that has been performed for the test case. If a pass indication is received for the test case, the test case is marked as passed. Also, in response to receiving the pass indication for the test case, a plurality of steps for the test case are automatically marked as passed. If a fail indication is received for the test case, a request for the user to identify a step that failed the manual test is output. When the response indicating which step failed is received, that step is marked as failed.