Automated Test Generation via Segmented Model and Description
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for producing test descriptions are inefficient, overly complex, and prone to errors, particularly in generating automated test scripts for software applications, due to the need for detailed models that require extensive knowledge and are difficult to maintain, leading to incomplete coverage of possible pathways and operational scenarios.
Innovation Solution
A method is introduced that defines a model of the system under test with representative states and actions, allowing for the creation of automated tests by associating operation commands with these model actions, enabling modular testing and high coverage of use scenarios with reduced effort, using a sequence of model actions and test description sections to generate operation commands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If detailed full models are used to generate automated test scripts, then measurement precision and coverage of test scenarios improve, but device complexity and difficulty of maintenance increase significantly
Solution Approach 1:
The patent segments the testing system into two distinct components: a simplified model that defines system states and transitions, and a separate test description that specifies test scenarios. This segmentation allows the model to remain simple and maintainable while the test description provides the necessary detail for comprehensive test coverage without increasing model complexity.
Solution Approach 2:
The patent extracts the test scenario specifications from the model itself and places them in separate test descriptions. This extraction allows the model to focus solely on defining system behavior states and transitions, while test scenarios are defined independently, reducing the complexity embedded in the model while maintaining comprehensive test coverage.
2Measurement precision
If detailed full models are used to generate automated test scripts, then measurement precision and coverage of test scenarios improve, but loss of time for model creation and maintenance increases
Solution Approach 1:
By segmenting the system into a simple reusable model and separate test descriptions, the patent enables independent maintenance of each component. The model requires minimal updates when system behavior changes, while test descriptions can be modified without affecting the model structure, significantly reducing maintenance time while preserving comprehensive test coverage.
Solution Approach 2:
The patent performs preliminary action by defining the system model once with its states and transitions, which then serves as a reusable foundation for generating multiple test scenarios. This preliminary model definition eliminates the need to recreate detailed models for each test, reducing repetitive maintenance work while ensuring consistent test coverage.
3Productivity
If traditional automated test generation methods are used, then productivity is reduced due to manual script creation, but device complexity increases due to detailed modeling requirements
Solution Approach 1:
The patent introduces an intermediary component that automatically generates test scripts from the simple model and test descriptions. This intermediary eliminates the need for manual script creation (improving productivity) while requiring only simple models rather than detailed complex models (reducing modeling complexity). The intermediary handles the complexity of script generation internally while presenting a simple interface to users.
Data Source
AI summary
A method for generating an automated test configured to test a system under test. The system under test has a plurality of operational states, at least one operational state having one or more executable actions associated therewith operable to execute predetermined operations and/or transition the system under test between operational states. The method includes the steps of: defining a model of the system under test comprising a plurality of model states; defining one or more selectable model actions; associating one or more test description sections with one or more model actions; selecting a sequence of model actions; and utilising the test description sections associated with the selected sequence of model actions to define a sequence of operation commands for execution on the system under test as an automated test.