Transformation Accelerator for Web Stress Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current stress-testing methods for web-based applications are costly and inefficient, as they require specialized performance test cases and are computationally intensive, limiting the capacity and duration of tests, especially with increasing system performance and throughput.
Innovation Solution
A system using a transformation accelerator to manipulate functional-test templates into transactions, which are sent to the system-under-test, allowing for the generation of complex workloads without full transaction requests, and queuing results for analysis, utilizing XML accelerators and XSLT to enhance scalability and reusability of test profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional commercial performance testing software is used to analyze results of each transaction as received, then comprehensive performance analysis is achieved, but computational load increases and system capacity is limited
Solution Approach 1:
The patent applies preliminary action by transforming functional test templates into performance test transactions before actual execution. The transformation accelerator pre-processes test templates into optimized transaction formats, preparing the test infrastructure in advance to handle high-volume transactions efficiently without computational bottlenecks during actual testing
Solution Approach 2:
The transformation accelerator serves as an intermediary component between functional test software and the system under test. It translates functional test templates into performance-optimized transactions, enabling the system to handle high-volume testing while maintaining analysis capabilities without being overwhelmed by computational load
2Reliability
If specialized performance test cases are created to generate high-load traffic, then effective stress-testing is achieved, but testing cost and complexity increase
Solution Approach 1:
The patent applies universality by enabling functional test templates to serve dual purposes - both functional validation and performance stress-testing. The transformation accelerator allows the same test templates to be reused for both functional testing and high-load performance testing, eliminating the need for separate specialized performance test cases and reducing overall test complexity
Solution Approach 2:
The transformation accelerator creates optimized copies of functional test templates transformed into performance test transactions. Instead of writing entirely new specialized performance test cases, the system copies and transforms existing functional templates, maintaining test coverage while reducing the complexity of creating specialized performance tests
3Productivity
If functional test cases are reused for performance testing, then testing cost is reduced, but the ability to generate required test scale is limited
Solution Approach 1:
The transformation accelerator applies parameter changes by modifying functional test templates through transformation rules that adjust test parameters for high-load scenarios. It transforms standard functional test parameters into performance-optimized parameters, enabling the same test cases to scale to the required test volumes while maintaining cost efficiency
4Reliability
If advanced computing clusters are used to generate sufficient tests to break the system, then system bottlenecks are identified, but infrastructure cost and complexity increase
Solution Approach 1:
The transformation accelerator acts as an intermediary that enhances the capability of standard computing infrastructure to generate sufficient test loads. By transforming and optimizing test transactions, it enables existing systems to achieve the test scales needed to break the system under test without requiring advanced computing clusters
Data Source
AI summary
One embodiment of the present invention provides a system that facilitates testing a system-under-test with functional-test software and a transformation accelerator. During operation, the system receives a functional-test template at the transformation accelerator. The system also receives a test signal at the transformation accelerator, wherein the test signal comprises testing parameters. Next, the system manipulates the functional-test template at the transformation accelerator according to the testing parameters to create one or more functional-test transactions. The system then sends the one or more functional-test transactions to the system-under-test. Next, the system receives results for the one or more functional-test transactions from the system-under-test. Finally, the system queues the results.