Web Service Testing Effort Estimation via Complexity Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Estimating the effort required for testing web services in an enterprise system is challenging due to the loosely coupled and highly interoperable nature of web service operations, which makes it difficult to accurately determine the number of test cases and time needed for testing, especially when considering individual and sequence combinations of operations.
Innovation Solution
A configuration data system that specifies complexity levels of web service operations and corresponding test cases, allowing for the determination of complexity levels based on input, output parameters, transformations, and downstream interactions, and calculating total test cases and efforts required for testing by examining this data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web service operations are designed to be loosely coupled and highly interoperable, then adaptability and versatility are improved, but device complexity and difficulty of detecting and measuring increase
Solution Approach 1:
The patent segments the web service testing process into distinct complexity levels (simple, moderate, complex) based on the number of operations and their interdependencies. By categorizing services into these segments, the system manages complexity through structured classification rather than treating all services uniformly, thereby maintaining interoperability while making complexity measurable and manageable.
Solution Approach 2:
The patent introduces quantitative parameters to measure and classify web service complexity, including the number of operations, sequence combinations, and dependency relationships. By changing the parameter of complexity measurement from qualitative to quantitative, the system can accurately assess and manage the increased complexity arising from high interoperability and loose coupling.
2Adaptability or versatility
If the number of web service operations and their sequence combinations increase, then functionality and versatility are improved, but the effort and time required for testing increase
Solution Approach 1:
The patent performs preliminary analysis of web service operations to identify sequence combinations and dependencies before actual testing begins. By pre-calculating the complexity level and required test cases based on operational sequences, the system prepares testing strategies in advance, reducing the time required during actual execution while maintaining comprehensive functionality coverage.
Solution Approach 2:
The patent applies partial testing strategies by focusing on the most critical sequence combinations and operations based on their complexity classification. Rather than exhaustively testing all possible sequences equally, the system identifies and prioritizes key test paths, thereby reducing overall testing time while still verifying essential functionality and interoperability.
3Measurement precision
If comprehensive test cases are designed to cover all web service operations and sequences, then measurement precision and reliability are improved, but device complexity and resource requirements increase
Solution Approach 1:
The patent applies local quality by tailoring the depth and scope of test cases to the specific complexity level of each web service operation and sequence. Rather than applying uniform comprehensive testing to all operations, the system adjusts testing intensity locally based on identified dependencies and criticality, thereby maintaining high measurement precision for critical paths while reducing unnecessary complexity in less critical areas.
Data Source
AI summary
An aspect of the present disclosure estimates effort required for testing web services deployed in an enterprise system. In one embodiment, a configuration data specifying complexity levels of web service operations and a number of test cases required for each of the complexity levels is maintained. Upon receiving data specifying a web service (deployed in the enterprise system) sought to be tested, a definition of the web service is inspected to identify web service operations provided by the web service. For each web service operation, a complexity level is determined, and a corresponding number of test cases required to be prepared for the determined complexity level is identified by examining the configuration data. A total number of test cases that is required to be prepared for testing the web service is then computed based on the identified number of test cases for the web service operations of the web service.