Test Case Validity Checking for Model-Based Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex software systems, such as ERP systems, require efficient testing methods due to their complexity, and existing model-based testing approaches often result in significant changes to test suites with minor changes to the test model, leading to inefficiencies in maintaining valid test cases across system versions.
Innovation Solution
A test system that includes a test model editor, scenario editor, script recorder, and optimizer, which assesses and validates test cases by comparing structural elements and data configurations between old and new test models, identifying structurally valid test cases and generating manipulated test models to ensure compatibility with new system versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If model-based test generators optimize test cases towards minimal number of executed test steps or minimal number of test cases, then test suite size is reduced, but even minimal changes to the test model result in completely different generated test suites
Solution Approach 1:
The patent performs preliminary actions by identifying and marking test cases as valid or invalid before the actual test execution. The system proactively assesses test case validity against the new test model structure and data configurations, preparing the test suite in advance to maintain consistency across model changes.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring and assessing test case validity when the test model changes. The optimization module receives feedback about which test cases remain valid and which become invalid, allowing the system to adjust the test suite dynamically while maintaining consistency and avoiding complete regeneration.
2Reliability
If manual testing is used to systematically test ERP systems, then testing can be performed, but manual testing is not practicable due to the involved complexity
Solution Approach 1:
The patent introduces an intermediary optimization module that acts as a mediator between the test model and test case execution. This module automatically assesses test case validity, manages test suite composition, and handles the complexity of model changes, making systematic testing of complex ERP systems practicable without manual intervention.
Solution Approach 2:
The system implements self-service capabilities where the optimization module automatically manages test case validation and suite optimization without requiring manual testing. The system autonomously handles complexity by programmatically assessing test case validity against model changes and maintaining comprehensive test coverage.
3Reliability
If test suites are completely regenerated after minimal changes to the test model, then test case validity is ensured, but extensive re-generation increases testing time and resource consumption
Solution Approach 1:
The patent applies partial action by selectively validating and optimizing only the necessary portions of the test suite rather than completely regenerating everything. The system performs targeted assessments of test case validity against model changes, applying optimization only where needed to maintain reliability while minimizing time loss.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Automated checking of test cases when the underlying test model has been modified includes verifying the structure of the original test cases against the new (modified) test model. Verified test cases are assessed by manipulating the new test model to produce corresponding manipulated test models. A test case is still valid for the new test model if a test case can be generated from its corresponding manipulated test model.