Context-Aware Defect Reporting in Application Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During application testing, the same defects are often reported multiple times by different testers, leading to an inflated number of reported defects and inefficiencies due to the need for context switching between testing and defect reporting systems, which pauses and resumes the testing process, increasing the time required for defect reporting.
Innovation Solution
A defect reporting system that allows users to view, accept, reject, and add defects in context with the testing instance without pausing the application, aggregating user inputs to eliminate duplicates and irrelevant defects, and enabling new defect reporting through an add-defect GUI while the application is running.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If defects are reported through a separate defect reporting system, then defect reporting functionality is provided, but context switching between testing and defect reporting systems is required, which pauses and resumes the testing process, increasing the time required for defect reporting
Solution Approach 1:
The patent merges the defect reporting functionality with the application testing interface by displaying a list of previously reported defects in a display layer over the testing instance. This allows testers to view, accept, or reject defects directly within the testing context without switching to a separate defect reporting system, thereby eliminating context switching and reducing the time required for defect reporting while maintaining ease of operation.
2Reliability
If multiple persons test the application, then comprehensive testing is achieved, but the same defects are reported several times, leading to duplication of defect reports
Solution Approach 1:
The patent implements a feedback mechanism where the system displays previously reported defects to current testers. When a tester views the list of previously reported defects and selects to accept or reject a defect, the system aggregates this feedback. This feedback loop enables multiple testers to work together while the system tracks and eliminates duplicate reports, maintaining comprehensive testing coverage while reducing the quantity of redundant defect reports.
3Loss of information
If a list of previously reported defects is displayed over the testing instance, then defect information is available in context, but the display layer must be managed to ensure only relevant defects are shown
Solution Approach 1:
The patent segments the defect information display by organizing previously reported defects into a structured list that can be selectively displayed over the testing instance. The system allows testers to view individual defects or groups of defects, and to accept or reject specific defects. This segmentation approach provides comprehensive defect information in context while simplifying display layer management through organized, modular presentation of defect data.
Data Source
AI summary
The present subject matter relates to defect reporting in application testing. In an implementation, a category of application testing is determined based on a testing instance of an application. The category of application testing is indicative of an aspect of the application, being tested. A list of previously reported defects associated with the determined category of application testing is displayed in a display layer over the testing instance of the application. A first user-input indicative of one of acceptance and rejection of a previously reported defect, from the list, with respect to the testing instance of the application is received. The first user-input is aggregated with previous user-inputs indicative of one of acceptance and rejection of the previously reported defect. It is determined whether the previously reported defect is irrelevant to the testing instance of the application based on the aggregation.