Test Case Generation for Partial Design Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional model-based testing methods are ineffective when dealing with software that has a partial or absent design model, as the input/output boundaries of the software code do not match those of the high-level model, making it difficult to achieve comprehensive test coverage.
Innovation Solution
A method and system for automatically generating test cases that align with a partial design model by identifying corresponding variables in the software under test, using a host machine to extract and generate test cases that meet specific coverage criteria, and employing forward/backward propagation or heuristic-based techniques to ensure complete test coverage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If conventional model-based testing methods are used, then test case generation is automated and broad coverage is achieved, but the method becomes ineffective when the software I/O boundary does not match the model I/O boundary
Solution Approach 1:
The patent segments the test case generation process into two distinct phases: (1) generating test cases at the model level using conventional MBT, and (2) mapping these test cases to the software boundary using forward/backward propagation. This segmentation allows each phase to operate independently on its own boundary, resolving the mismatch issue.
Solution Approach 2:
The patent introduces an intermediary mapping process that acts as a bridge between the model boundary and the software boundary. This intermediary uses forward propagation (from model inputs to software inputs) and backward propagation (from software outputs to model outputs) to translate test cases across different boundaries, enabling conventional MBT to work with partial design models.
2Ease of manufacture
If the model boundary matches the software boundary, then conventional MBT can be applied directly, but this requirement limits practical applicability when models are partial or absent
Solution Approach 1:
The patent makes the test case generation process dynamic by allowing the model boundary to differ from the software boundary. The forward/backward propagation mechanism dynamically adjusts the mapping between boundaries based on the specific partial model available, rather than requiring a fixed matching relationship.
Solution Approach 2:
The patent creates a universal test case generation approach that can handle multiple scenarios: complete models, partial models, and even cases where only some portions of software have corresponding models. The mapping mechanism provides multi-functionality by adapting to different model completeness levels.
3Measurement precision
If manual generation of test cases is performed, then precise coverage can be achieved, but the time and effort required increases significantly
Solution Approach 1:
The patent performs preliminary automated test case generation at the model level before mapping to the software boundary. This preliminary action creates a foundation of test cases that can then be systematically mapped, reducing the need for manual generation while maintaining precision through the structured mapping process.
Solution Approach 2:
The backward propagation mechanism provides feedback from the software output boundary to the model input boundary, allowing the system to automatically refine and adjust test cases to achieve precise coverage. This feedback loop replaces manual adjustment while maintaining precision.
Data Source
AI summary
A method allows for testing software under test (SUT) with respect to a partial design model (PDM) having a boundary which differs from a boundary of the SUT. The method includes recording input information including the SUT, the PDM, and coverage criteria defining a required number of the test cases. Variables in the SUT are identified that correspond to boundary signals for the PDM. Test cases are extracted meeting the coverage criteria. The method may include generating additional test cases at the PDM level and mapping the additional cases with corresponding constraint functions to the boundary of the SUT using a forward/backward propagation and/or heuristics guided technique. A system for testing the SUT includes a host machine and memory. The host machine executes process instructions from memory to identify variables in the SUT that correspond to boundary signals for the PDM, and extracts test cases meeting the coverage criteria.