Feature Interaction Continuity Testing for Software
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software testing is labor-intensive, especially for complex software, and expert testing methods vary in depth among engineers, leading to inefficiencies and burnout, with many high-severity defects being found late in the process.
Innovation Solution
The method of feature interaction continuity testing automatically generates expert testing scenarios by identifying software application features and their interactions, storing test definitions in a database, and generating a testing plan that sequences these definitions for efficient defect detection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automated testing platforms are used to increase testing efficiency, then productivity is improved, but the complexity of managing and generating comprehensive test scenarios increases
Solution Approach 1:
The patent segments the testing process into distinct components: feature identification, interaction modeling, test definition generation, and test execution. Each component is handled separately by the system, breaking down the complex task of comprehensive software testing into manageable segments that can be automated and tracked individually.
Solution Approach 2:
The patent introduces an intermediary testing plan generation system that acts as a mediator between the software features and the test execution. This system automatically generates testing plans by identifying feature interactions and sequencing test definitions, reducing the direct complexity burden on test engineers while maintaining comprehensive coverage.
2Measurement precision
If expert testing methods are used to improve defect detection quality, then measurement precision is improved, but loss of time increases due to varying engineer depth and burnout
Solution Approach 1:
The patent implements self-service through automated test definition generation and sequencing. The system automatically identifies feature interactions, generates appropriate test definitions, and creates optimized test execution plans without requiring constant expert engineer intervention. This maintains high defect detection quality while reducing time loss associated with human variability and burnout.
Solution Approach 2:
The patent performs preliminary actions by pre-identifying all feature interactions and pre-generating comprehensive test definitions before execution. The system analyzes the software model in advance to create a complete testing plan, ensuring high measurement precision for defect detection while reducing the time needed during actual test execution.
3Reliability
If comprehensive test coverage is pursued to improve reliability, then reliability is improved, but productivity decreases due to labor-intensive manual testing
Solution Approach 1:
The patent replaces the mechanical system of manual test creation and execution with an automated computational system. The system automatically identifies feature interactions, generates test definitions, sequences tests optimally, and executes them programmatically. This substitution maintains comprehensive test coverage for improved reliability while dramatically increasing productivity through automation.
Solution Approach 2:
The patent changes key parameters from manual processes to automated ones: test definition generation is transformed from manual expert creation to algorithmic generation based on feature interactions; test sequencing is changed from manual planning to automated optimization; and execution is transformed from manual operation to automated runtime processing. These parameter changes enable both high reliability and productivity.
Data Source
AI summary
A method including: storing, in a memory, a test database, the test database including a plurality of test definitions, each test definition being associated with a respective base application feature and a respective destination application feature; detecting a request to generate a testing plan; generating the testing plan in response to the request, the testing plan being generated by using the test database, the testing plan identifying a sequence of at least some of the test definitions that are part of the test database; and outputting an indication of the testing plan for presentation to a user.