Automated Integration Regression Detection via Historical Message Baselines

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users integrating on-premises applications with cloud applications via middleware systems face challenges in identifying integration regressions caused by updates to the middleware mapping, leading to potential breakdowns in integration without clear identification of the source changes.

Innovation Solution

A test management system generates and executes test cases based on previously transmitted messages to identify and diagnose integration regressions between on-premises and cloud applications, creating a test suite from baseline messages to determine the specific cause of integration issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a third-party middleware system is used to integrate on-premises applications with cloud applications, then flexibility and accessibility are improved, but integration reliability deteriorates because the user cannot quickly identify mapping updates that cause integration regressions

Engineering Contradiction:

ImproveflexibilityVSAvoidintegration reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically generating test cases from historical messages before integration regressions occur. Test suites are created in advance based on baseline mappings, enabling proactive detection of potential integration issues before they impact production systems.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by automatically comparing current integration behavior against baseline test results. When mapping updates occur in the third-party middleware, the system executes test suites and provides feedback about integration regressions, enabling users to identify and respond to issues quickly.

Inventive Principle:

Principle #23Feedback

2Reliability

If manual test case design is used to identify integration regressions, then testing coverage can be comprehensive, but time consumption and operational complexity increase significantly

Engineering Contradiction:

Improveintegration stabilityVSAvoidtime consumption

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by automatically generating test cases from historical messages without requiring manual intervention. The test management system autonomously creates test suites, executes them, and identifies integration regressions, eliminating the need for users to manually design and execute comprehensive test cases.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system uses copying by replicating historical message patterns to generate test cases. Instead of manually creating test scenarios, the system copies real message structures and data from production history to automatically generate comprehensive test suites that cover actual integration scenarios.

Inventive Principle:

Principle #26Copying

3Reliability

If comprehensive test cases are created to cover both standard and customized content, then testing completeness is improved, but device complexity and ease of operation worsen due to manual test case management

Engineering Contradiction:

Improvetesting completenessVSAvoidtest case management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system achieves universality by creating a multi-functional test management platform that handles both standard and customized content through a single automated framework. The system universally applies test generation algorithms to different message types and integration scenarios, eliminating the need for separate manual test case management processes.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses copying to replicate historical message patterns across different test scenarios. By copying real message structures from production systems, the automatically generated test cases inherently cover both standard and customized content, ensuring testing completeness without manual intervention.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20210165728A1Intelligent automated way of baselining integration content using messages from historical tests to be used for regression testing

Publication Date: 2021.06.03 SAP SE

AI summary

Disclosed herein are system, method, and computer program product embodiments for determining an integration regression between a source system and a target system. An embodiment operates by selecting a first set of messages in a middleware system. The embodiment receives a baseline mapping for the first set of messages from the middleware system. The embodiment creates a test suite based on the first set of messages. The embodiment performs the test suite, wherein the performing generates a second set of messages in the middleware system and a current mapping for the second set of messages. The embodiment compares the first set of messages to the second set of messages based on the baseline mapping and the current mapping. The embodiment determines an integration regression between the source system and the target system based on the comparing.