Testing Module for Rule Validation in Complex Software Chains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Testing specific rules in a live production environment is challenging due to complex chains of output dependencies among modules, requiring testers to fix output values for each module to ensure rule criteria are met.
Innovation Solution
A testing module is implemented to preload predetermined output values into the database, allowing the system to switch to simulation mode, where test information requests are sent to downstream modules, which retrieve and provide predetermined outputs, enabling the decisioning module to apply rules and generate output decisions for testing purposes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If testers fix output values for each module in the complex chain of dependencies to test a specific rule, then the rule testing can be performed, but the testing process becomes extremely complex and time-consuming
Solution Approach 1:
The patent introduces a testing module as an intermediary component that sits between the test initiator and the complex chain of downstream modules. This testing module automatically manages the fixation of output values for all modules in the dependency chain, shielding testers from the complexity while ensuring accurate rule testing. The intermediary handles the coordination of multiple modules' output values based on the test scenario requirements.
Solution Approach 2:
The system performs preliminary actions by pre-configuring and storing multiple test scenarios that define the expected output values for each module in the dependency chain. Before actual rule testing begins, these scenarios are prepared in advance, including the fixation of all necessary output values across the module chain. This preliminary setup eliminates the need for manual coordination during testing execution.
2Reliability
If testers manually fix output values for multiple downstream modules to test a rule, then the rule criteria can be satisfied, but the time required for testing increases significantly
Solution Approach 1:
The testing module implements self-service by automatically selecting and applying appropriate test scenarios based on the rule being tested. It autonomously fixes the output values for all downstream modules without requiring manual intervention from testers. The system serves itself by managing the entire testing workflow, from scenario selection to result validation, dramatically reducing testing time while maintaining completeness.
Solution Approach 2:
The system uses pre-defined test scenarios that copy proven testing patterns and configurations. Instead of manually creating and coordinating output values for each test case, testers can reuse and adapt existing scenario templates. This copying approach ensures all necessary module outputs are correctly configured while eliminating repetitive manual work.
3Reliability
If the system uses the complex chain of downstream modules to determine rule triggering, then accurate rule execution is achieved, but testing becomes difficult due to multiple levels of output dependencies
Solution Approach 1:
The patent segments the complex testing problem into two distinct parts: the rule execution logic (which remains intact and accurate) and the testing control logic (which is simplified through the testing module). The testing module handles the complexity of coordinating downstream module outputs, while the rule engine continues to execute rules accurately based on the provided inputs. This segmentation isolates the complexity from the testers while preserving rule execution accuracy.
Solution Approach 2:
The testing module acts as an intermediary layer that simplifies the interface between testers and the complex downstream module chain. It translates high-level test requirements into the specific output value configurations needed across multiple modules. This intermediary shields testers from the complexity of the dependency chain while ensuring the rule engine receives accurate inputs for reliable execution.
Data Source
AI summary
A method may include receiving a request for an output decision corresponding to a set of input parameters, the request including a test indication. The method also includes determining that the output decision is dependent on an output of a first module that is configured by default to communicate with a second module, the output of the first module being dependent on the output of the second module. Further, the method includes based on the test indication, causing the first module to transmit an information request to a simulation module, the simulation module identifying a predetermined output value corresponding to the first module in response to the information request. The method also includes generating the output decision according to a decisioning rule that is triggered based on the predetermined output value and transmitting the output decision to a testing module.