Business Logic Validation via Test Harness Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Customers implementing business logic in Enterprise Software Systems often introduce untested routines that can lead to system instability and data corruption, as they may not be well-versed in the internal workings of the software, resulting in performance issues and the need for costly support from providers.
Innovation Solution
A method and system for validating business logic by translating it into an executable routine, using a test harness to generate result sets, and determining deployment readiness, combined with administrator approval, to ensure reliability and monitor performance, with features like cycle detection in directed graphs and failure threshold management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If customers implement business logic routines without thorough testing, then the system allows flexibility and ease of operation, but system stability and reliability deteriorate due to untested code causing database corruption and performance issues
Solution Approach 1:
The system performs preliminary testing of business logic routines before deployment to production. A test harness automatically executes test cases against the routine, and only routines passing validation are deployed. This preliminary action prevents unstable code from reaching production while maintaining ease of implementation.
Solution Approach 2:
The system provides feedback to customers about the testing status and reliability of their business logic routines. The test harness returns results indicating whether a routine passes or fails validation, enabling customers to adjust their routines accordingly while maintaining simple implementation processes.
2Reliability
If automated testing and validation processes are implemented, then system reliability improves through prevention of database corruption, but device complexity increases due to additional validation layers
Solution Approach 1:
The test harness performs self-contained automated testing of business logic routines without requiring manual intervention. The system automatically executes test cases, compares results against expected outcomes, and determines deployment eligibility. This self-service approach improves reliability while minimizing the complexity increase through automation.
Solution Approach 2:
The test harness acts as an intermediary layer between customers and the production system. It validates business logic routines before they reach the database, absorbing complexity in a dedicated validation layer that protects the core system from corrupted code while maintaining simplicity at the user interface level.
3Productivity
If business logic routines are deployed without validation, then productivity and ease of operation improve, but harmful factors increase due to untested code causing system failures and performance bottlenecks
Solution Approach 1:
The system performs preliminary validation of business logic routines before deployment. The test harness automatically executes comprehensive test cases and only approves routines that pass validation. This preliminary action maintains high deployment productivity while preventing harmful failures by filtering out defective code.
Solution Approach 2:
The validation system provides immediate feedback to customers about the quality and safety of their business logic routines. This feedback mechanism enables rapid iteration and correction of problematic routines while maintaining fast deployment cycles, as only validated routines proceed to production.
Data Source
AI summary
A method of implementing and validating business logic may include translating the business logic into an executable routine, and providing the executable routine to a logic interpreter. The logic interpreter may be configured to receive inputs from the user interface during live use, process the inputs according to the executable routine to generate a result set, and provide the result set to a database for storage. The method may also include receiving a test harness comprising a plurality of input sets and a corresponding plurality of expected result sets, and processing each of the plurality of input sets according to the executable routine to generate a plurality of result sets. The method may additionally include generating an automatic determination as to whether the executable routine should be deployed for live use based on the plurality of result sets and the plurality of expected result sets.