Test Orchestration Engine for Automated Multi-Tier Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Automated testing of end-to-end transactions across multiple tiers in a brokerage firm's system is time-consuming and requires extensive training for quality assurance staff due to the use of numerous tools and thousands of lines of custom test code.
Innovation Solution
A test orchestration engine that generates metadata code artifacts from human-readable configuration files, allowing for code-free testing across multiple technologies and roles, with separate models for test scripts, application-specific attributes, and context parameters, enabling sequential or parallel testing activities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If numerous tools are used to test various systems involved in transactions, then testing coverage is improved, but training time for quality assurance staff increases
Solution Approach 1:
The patent creates a universal testing framework that can test multiple disparate systems (user interfaces, middle-tier application servers, databases, middleware, mainframe systems) through a single unified interface. This framework provides multi-functionality by handling various testing needs across different technology stacks without requiring separate specialized tools, thereby reducing training time while maintaining comprehensive testing coverage.
Solution Approach 2:
The testing framework acts as an intermediary layer between the tester and the complex multi-tier system. It abstracts the complexity of underlying systems and tools, providing a simplified interface for quality assurance staff to execute tests without needing to understand or be trained on numerous underlying testing tools and technologies.
2Reliability
If thousands of lines of custom test code are written to test disparate systems, then testing capability is improved, but maintenance complexity increases
Solution Approach 1:
The patent segments the testing capability into modular components that can be independently configured and maintained. Instead of requiring thousands of lines of custom test code, the framework divides testing functionality into separate, reusable elements that can be assembled through configuration files, significantly reducing maintenance complexity while preserving comprehensive testing capability.
Solution Approach 2:
The framework enables testing capability to be configured through parameter changes in configuration files rather than requiring code modifications. This allows testing behavior to be adjusted by changing parameters and settings without modifying the underlying test infrastructure, thereby maintaining testing capability while reducing maintenance complexity.
3Ease of operation
If a unified testing framework is implemented across multiple technologies, then ease of operation is improved, but system complexity increases
Solution Approach 1:
The patent extracts the complexity of multi-technology testing into a separate, standalone framework that operates independently from the systems being tested. This extracted framework handles the complexity of interfacing with multiple technologies internally, while presenting a simplified interface to users, thereby improving ease of operation without adding visible system complexity.
Solution Approach 2:
The framework creates virtual representations or models of the actual systems being tested, allowing tests to be executed against these copies rather than the live systems. This copying approach simplifies operation by providing a controlled testing environment while managing system complexity through abstraction.
Data Source
AI summary
Computer systems and methods test applications of an enterprise computer system. The enterprise computer system comprises a test orchestration engine that is configured to receive a human-readable configuration file that comprises: a test script model that specifies testing activities for an application of the enterprise computer system; an application model that specifies attribute values for the application for the testing of the application; and a script model that specifies context parameters for the testing of the application. The test orchestration engine generates, at compile time, metadata code artifacts from the configuration file; and orchestrate, at run time, testing of the application based on the metadata code artifacts generated from the configuration file.