Test Engine Selecting Cases by Configuration Settings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manual testing of enterprise resource planning (ERP) applications after configuration modifications is time-consuming and lacks consistency, as it relies on individual adherence to test cases, making it inefficient and prone to errors.
Innovation Solution
A test engine that dynamically identifies and executes test cases based on application configuration settings and scoping information, separating application configuration from execution environments, and utilizing a configuration scoping application to determine relevant test areas through adaptation catalog entries and rules, ensuring thorough and automated testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual testing is performed by users according to defined test cases, then testing can be performed with simple tools and processes, but the testing is time-consuming and the quality is inconsistent
Solution Approach 1:
The system enables self-service automated testing where the testing process executes itself without manual intervention. The automated testing engine selects and executes relevant test cases based on configuration data, eliminating the need for manual test execution while ensuring consistent quality across all testing operations.
Solution Approach 2:
The system dynamically changes testing parameters by automatically selecting which test cases to execute based on the specific configuration data being tested. This allows the testing process to adapt to different configurations without manual reconfiguration, maintaining consistency while reducing time through automated parameter selection.
2Reliability
If comprehensive test cases are defined for all functionality, then all functionalities can be tested, but the testing scope becomes too large and time-consuming
Solution Approach 1:
The system extracts only the relevant test cases from the complete test suite based on the configuration data being tested. By taking out only the necessary subset of test cases rather than executing all possible tests, the system maintains comprehensive coverage of relevant functionalities while significantly improving testing efficiency.
Solution Approach 2:
The system performs partial action by executing only the specific test cases relevant to the current configuration rather than all possible test cases. This selective approach ensures adequate testing coverage for the specific functionality being tested while avoiding the excessive time consumption of running the entire test suite.
3Ease of operation
If manual testing is performed, then flexibility in testing approach is maintained, but the process lacks automation and consistency
Solution Approach 1:
The automated testing system provides multi-functionality by handling various configuration types and test case selections through a single automated engine. This universal approach maintains flexibility in testing different scenarios while consistently applying automated processes, eliminating the need for manual intervention across different testing situations.
4Adaptability or versatility
If configuration settings are modified, then the application can be customized for different organizations, but the configuration must be re-tested
Solution Approach 1:
The system performs preliminary action by pre-defining all possible test cases and organizing them in a structured test library. When configuration changes occur, the system quickly selects the relevant pre-defined test cases rather than creating new tests, enabling rapid re-testing that supports frequent customization while minimizing re-testing time.
Data Source
Figure 1~2A
Figure 2B
Figure 3
AI summary
The present subject mater relates to testing software application configurations and, more particularly, to a test engine. The various embodiments described and illustrated herein provide systems, methods, and software that maintain a configuration database in a memory, wherein the configuration database includes a representation of configuration settings of an application. Some such embodiments may further store a test engine module in the memory, wherein the test engine module includes a set of test cases, which when processed, test functionality of the application, wherein a test case is selected for execution as a function of one or more application configuration setting representations from the configuration database.