Automated Web Service Testing via Data Model Retrieval

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Modern web services, despite conforming to industry standards, often mask complex back-end systems that require extensive testing and maintenance, making it challenging to validate data and functionality through their public interfaces.

Innovation Solution

The Test Anything Protocol (TAP) system automatically tests web services by retrieving data models and accessing individual data records, verifying field types and values, and performing CRUD operations to ensure data integrity and functionality, independent of the data type or service provider.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If web services use standardized protocols (SOAP/WSDL) to define interfaces, then interoperability and ease of operation are improved, but device complexity and difficulty of detecting back-end functionality worsen

Engineering Contradiction:

Improveease of operationVSAvoiddevice complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The test system automatically retrieves the data model from the web service itself and uses it to generate test cases, eliminating the need for manual test case creation and reducing dependency on human expertise about the service's internal data structures

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary test system that sits between the tester and the web service, using the data model as a mediator to translate high-level service definitions into comprehensive test cases that cover back-end functionality

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If web services mask complex back-end systems behind standardized interfaces, then ease of operation is improved, but measurement precision and reliability of validation worsen

Engineering Contradiction:

Improveease of operationVSAvoidmeasurement precision

Core Design Contradiction:

Ease of operationVSMeasurement precision

Solution Approach 1:

The test system performs preliminary actions by first retrieving and analyzing the data model before executing test cases, allowing it to understand the expected data structures and validation rules in advance

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by comparing actual web service responses against the retrieved data model, automatically identifying discrepancies between the standardized interface and the actual back-end behavior

Inventive Principle:

Principle #23Feedback

3Ease of manufacture

If manual testing methods are used to validate web service data, then ease of manufacture is maintained, but productivity and measurement precision worsen

Engineering Contradiction:

Improveease of manufactureVSAvoidproductivity

Core Design Contradiction:

Ease of manufactureVSProductivity

Solution Approach 1:

The test system is self-service in that it automatically retrieves the data model, generates test cases, executes tests, and reports results without requiring manual intervention, dramatically improving productivity while maintaining ease of implementation

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical testing processes with an automated system that uses programmatic retrieval of data models and algorithmic generation of test cases, substituting human effort with automated computational processes

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If comprehensive testing of back-end systems is performed, then reliability and measurement precision are improved, but loss of time and device complexity worsen

Engineering Contradiction:

ImprovereliabilityVSAvoidloss of time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary retrieval of the data model to understand the complete structure of expected data before testing, allowing for comprehensive test coverage without manually exploring each endpoint

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The test system is designed to be universal by working with any web service that provides a data model, using the same automated process to test different services without requiring service-specific test scripts or extensive customization

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10361944B2Automated test for uniform web service interfaces

Publication Date: 2019.07.23 ORACLE INT CORP

AI summary

A method of automated testing of a Web Service public interface may include retrieving a first data set from the Web Service. The first data set may include information for accessing individual data records stored by the Web Service. The method may also include retrieving a second data set from the Web Service. The second data set may include a data model for the individual data records. The method may additionally include retrieving a first data record from the Web Service using the information for accessing individual data records. The method may further include verifying that the first data record retrieved from the Web Service is correct by comparing fields in the first data record with the data model.