Software Application Testing Coverage Discrepancy Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software application testing often fails to accurately match usage patterns of market users, leading to discrepancies between testing coverage and market coverage, which can result in undetected defects and poor user experience.

Innovation Solution

A method and system that deploy software applications to initial testers, collect testing coverage data, and then deploy to market users to gather market coverage data, comparing both to identify discrepancies and select additional testers based on these findings to ensure comprehensive testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software application is tested only with initial testers having specific system configurations, then testing process is simple and quick, but testing coverage does not match market usage patterns

Engineering Contradiction:
Improvetesting coverage accuracyVSAvoidtesting process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by deploying the software application to a marketplace before formal testing, collecting market coverage data in advance. This preliminary deployment allows the system to gather information about actual usage patterns, system configurations, and feature usage by market users, which then informs the selection of testers and configuration of testing environments to better match market reality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by comparing market coverage data with testing coverage data to identify discrepancies. This comparison creates a feedback loop where the differences between actual market usage and testing coverage are measured, and this information is used to adjust and improve the testing process by selecting additional testers with appropriate system configurations to close the coverage gaps.

Inventive Principle:
Principle #23Feedback

2Productivity

If software application is deployed to marketplace before comprehensive testing, then time to market is reduced, but defects may be undetected

Engineering Contradiction:
Improvedeployment speedVSAvoiddefect detection rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs a preliminary deployment to the marketplace to collect usage data before conducting comprehensive testing. This preliminary action enables the organization to understand actual market usage patterns, which then informs more targeted and effective testing strategies that can identify defects more efficiently while maintaining fast deployment cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from comparing market coverage data with testing coverage data to continuously improve defect detection. By analyzing discrepancies between how the application is used in the marketplace versus how it is tested, the system can identify gaps in testing coverage and adjust testing strategies to better detect defects that occur in real market conditions.

Inventive Principle:
Principle #23Feedback

3Reliability

If additional testers are selected based on coverage discrepancy, then testing coverage is improved, but testing cost and time increase

Engineering Contradiction:
Improvetesting coverageVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis by collecting market coverage data before finalizing the testing plan. This preliminary action allows the system to identify which system configurations and feature usage patterns are most prevalent in the marketplace, enabling the selection of testers that maximize testing coverage efficiency from the outset rather than requiring extensive additional testing later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies partial action by selecting additional testers specifically targeted at closing identified coverage gaps rather than conducting exhaustive testing with all possible configurations. By focusing testing efforts on the specific areas where coverage discrepancies exist, the system achieves improved testing coverage without the time and resource cost of comprehensive testing across all possible scenarios.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10459828B2Method and system for software application testing recommendations
Publication Date: 2019.10.29 GOOGLE LLC
  • US10459828B2 patent drawing
  • US10459828B2 patent drawing
  • US10459828B2 patent drawing

AI summary

A method for application testing recommendation includes deploying a software application to first testers having first system configurations, and receiving testing coverage data describing (i) a first subset of features of the software application being tested by the first testers and (ii) information describing the first system configurations. The method further includes deploying the software application to a marketplace, and receiving market coverage data describing (i) a second subset of features being used by market users and (ii) second system configurations of the market users. The method further includes comparing the market coverage data and the testing coverage data to identify a coverage discrepancy, selecting second testers to test the software application based on the coverage discrepancy, and deploying the software application to the second testers.