Application Testing Time Prediction Profiles
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current quality testing processes for applications in app stores provide limited and inaccurate information to developers regarding testing progress, using generic overall testing times that fail to account for individual application characteristics.
Innovation Solution
Implementing customized processing time predictions by collecting and storing testing data associated with attribute values, defining profiles based on these attributes, and matching new applications to profiles for personalized prediction outputs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If generic/average overall testing times are used for all applications, then the information provided to developers is simple and consistent, but the accuracy of testing time predictions deteriorates
Solution Approach 1:
The patent segments the application testing process into multiple distinct stages (e.g., automated testing, manual review, certification). Each stage is assigned its own predicted duration based on historical data and application attributes. This segmentation allows the system to provide detailed, accurate predictions for each stage while maintaining overall simplicity through structured presentation.
Solution Approach 2:
The system changes the parameter of testing time prediction from a single generic value to multiple stage-specific values. By varying the prediction granularity and using different historical data parameters for different application types and testing stages, the system achieves both accuracy (through customized predictions) and simplicity (through consistent methodology).
2Measurement precision
If customized processing time predictions are implemented for different application profiles, then the accuracy of testing time predictions improves, but the complexity of the testing system increases
Solution Approach 1:
The patent implements a universal prediction system that handles multiple application types, testing stages, and profile categories through a single integrated model. The system uses consistent data structures and prediction algorithms that work across all profiles, reducing complexity despite the customized nature of predictions. The same infrastructure serves diverse prediction needs.
Solution Approach 2:
The system performs preliminary actions by pre-defining application profiles and categorizing applications before actual testing begins. Historical testing data is pre-processed and stored in association with profile attributes, enabling quick retrieval and prediction without complex real-time analysis. This preliminary organization reduces system complexity during operation.
3Reliability
If detailed stage-by-stage testing data is collected and stored, then the quality of prediction outputs improves, but the amount of data storage and processing requirements increases
Solution Approach 1:
The patent extracts only the essential attributes and timing data needed for prediction from the complete testing process. Instead of storing all raw testing data, the system extracts key profile attributes (application type, size, complexity) and corresponding testing stage durations. This extraction maintains prediction quality while significantly reducing storage requirements.
Solution Approach 2:
The system performs preliminary data organization by structuring and storing testing data in association with profile attributes before predictions are needed. Historical data is pre-aggregated and categorized, allowing efficient retrieval and processing without requiring extensive real-time data handling. This preliminary structuring reduces both storage needs and processing complexity.
Data Source
AI summary
Techniques for application quality testing time predictions are described that provide customized processing time predictions for application testing. Testing times for various stages of testing are collected during application testing. The collected testing data may be stored in association with various attribute values ascertained for the applications. The collected timing data is used to predict processing times for applications that match defined profiles. The profiles may be defined to include selected attributes and values used to identify applications having corresponding attributes and values. The collected timing data may be processed to derive predictions for processing times on a profile-by-profile basis. When a new application is submitted, the application is matched to a particular profile based on attribute values possessed by the application. Then, processing time predictions associated with the matching profile may be obtained, assigned to the application, and output for presentation to a developer of the application.


