Automated Test Script Binding for Payment Network Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for testing applications interfacing with payment networks require screen recordings after the application is complete, making it inefficient to construct and execute test scripts before or during development, and fail to detect unanticipated changes effectively.

Innovation Solution

A system and method that allow test scripts to be constructed based on application requirements prior to development, using an artifacts database to generate and bind test scripts to the application, and compare outputs to historical results to identify changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If screen recordings are used to construct test scripts after application completion, then test coverage can be achieved, but development time and release time are extended

Engineering Contradiction:
Improvetest coverageVSAvoidrelease time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent enables test scripts to be constructed before the application is complete by using application requirements and an artifacts database. Test engineers can define test procedures in advance based on requirements documents, and the system automatically binds these scripts to the application once it becomes available, eliminating the need to wait for application completion before starting test script construction.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an artifacts database as an intermediary between application requirements and test script construction. This database stores reusable test artifacts that can be automatically bound to applications, serving as a mediator that enables test script creation without requiring the application to be complete or requiring manual screen recording.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If traditional testing methods are used without change detection, then testing can be completed, but unanticipated changes in application behavior are not detected

Engineering Contradiction:
Improvetesting efficiencyVSAvoidchange detection capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism that compares current application outputs with historical test results to automatically detect changes. The system captures outputs from application executions, stores them in a database, and compares them with previously stored results, providing feedback about unanticipated changes in application behavior that would otherwise go undetected.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If test scripts are constructed manually after application release, then testing can be performed, but the process is time-consuming and inefficient

Engineering Contradiction:
Improvetest accuracyVSAvoidtest construction efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent enables test scripts to be automatically bound to applications and executed without manual intervention. The system self-services by automatically binding test scripts from the artifacts database to applications based on matching criteria, and by automatically comparing test results with historical data, eliminating the need for manual test script construction and change detection activities.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11093375B2Systems and methods for automating test scripts for applications that interface to payment networks
Publication Date: 2021.08.17 MASTERCARD INT INC
  • US11093375B2 patent drawing
  • US11093375B2 patent drawing
  • US11093375B2 patent drawing

AI summary

Systems and methods are provided for use in testing a target application, including target applications for a payment network. One exemplary computer-implemented method includes deploying, to a computing device hosting a target application, an application monitor and executing a test script directed to the target application during a test interval, where the test script defines an input to the target application and at least one expected output when the target application receives said input. The method also includes identifying an observation when the output of the target application, in response to said input, is different than the at least one expected output and communicating an observation flag to the application monitor. The method further includes receiving forensic details associated with the computing device and generated within a predefined interval of the observation, and storing the forensic details associated with the observation.