Automated Web Service Code Testing via Response Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity and frequency of updates in web service programming code require efficient and reliable automated testing to ensure proper functioning across various client devices and networks, as existing methods are often manual and time-consuming.

Innovation Solution

A system and method for automatically testing web service programming code by generating and processing large numbers of web service requests using a test server, comparing responses from production and new code versions, and identifying differences to determine functionality and stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual testing methods are used for web service code, then testing can be performed with simple tools, but testing efficiency is low and time consumption is high

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtime consumption
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables automated self-testing of web service code through a test engine that automatically generates test requests, executes them against the web service, and compares results without requiring manual intervention. The system serves itself by autonomously performing the complete testing workflow.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical testing operations with an automated electronic testing system. The test engine automatically generates test requests, transmits them through the network to the web service, and processes responses computationally, substituting human manual operations with automated electronic processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If web service code is updated frequently with complex features, then new functionalities are provided to users, but testing reliability becomes more difficult to ensure

Engineering Contradiction:
Improvenew functionalitiesVSAvoidtesting reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The test engine is designed with universal functionality to handle diverse web service code updates and complex features. It can generate various types of test requests, adapt to different web service interfaces, and perform multiple testing operations through a single unified system that works across different scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements feedback mechanisms by comparing test responses from updated code against expected results. The test engine receives responses from the web service, automatically analyzes them, and provides feedback on whether the updates maintain proper functioning, enabling continuous verification of reliability.

Inventive Principle:
Principle #23Feedback

3Reliability

If automated testing system generates and processes large numbers of web service requests, then testing coverage is improved, but system complexity increases

Engineering Contradiction:
Improvetesting coverageVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The testing system is segmented into distinct functional components: a test engine for generating and managing test requests, a response analysis module for processing results, and a comparison mechanism for verifying outcomes. This segmentation allows the system to handle large numbers of requests through specialized subsystems rather than a monolithic complex structure.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8793660B2Automated testing of programming code for a web service
Publication Date: 2014.07.29 CELLCO PARTNERSHIP INC
  • US8793660B2 patent drawing
  • US8793660B2 patent drawing
  • US8793660B2 patent drawing

AI summary

The testing of programming code for a web service, such as code for a web service application program or for a web service application programming interface (API), is automatically performed. A set of web service requests is generated based on potential input values for fields of the requests that are included in a spreadsheet. The web service requests are firstly processed via execution of a production version of the programming code to generate a set of production web service responses, where the production version of the programming code is assumed to generate accurate web service responses. The web service requests are then processed via execution of a new version of the programming code to generate a set of new web service responses. The web service responses of the new and production sets are compared to determine whether the new version of the programming code functions accurately.