# US 2018/0324222 A1 · Testing distributed applications that have an established exchange in an advanced message queuing protocol (amqp) message broker

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0324222 A1
- Document ID: US20180324222A1
- Status: Published application
- Kind: A1
- Application number: 15/587,791
- Filed: 2017-05-05
- Published: 2018-11-08
- Earliest claimed: 2017-05-05
- Assignees: Dell Products L.P.
- Applicants: Dell Products, L.P.
- Inventors: DONAL CARPENTER
- Web page: https://patentgrep.com/patent/US20180324222A1

## CPC

- H04B 17/19: Self-testing arrangements
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- H04L 67/55: Push-based network services
- H04L 67/562: Brokering proxy services
- H04L 67/63: Routing a service request depending on the request content or context
- H04B: TRANSMISSION
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for testing a distributed application. The method includes receiving the automation test code and initiating execution of the automation test code. A responsive event provided by at least one distributed application node, in response to execution of the automation test code is detected. One or more messages having a specified routing key are received as the responsive event. A queue for receiving the one or more messages generated on an advanced message queuing protocol message broker. A test context specific binding key having a known entity identifier and the specified routing key is selectively generated to form a bind between the queue and an established exchange. The one or more messages having a payload that selectively indicates the nature of the state change associated with the predetermined distributed event type are received at the queue. The one or more messages are selectively provided to a requesting device having access to the queue.

## Claims

### Claim 1

A method in an information handling system (IHS) for executing automation test code, the method comprising:
receiving the automation test code;
generating, on an advanced message queuing protocol (AMQP) message broker, a queue for receiving the one or more messages associated with a predetermined distributed event type;
selectively generating a test context specific binding key having a known entity identifier and the specified routing key, juxtapose to generating the queue, wherein the test context specific binding key forms a bind between the queue and an established exchange associated with the AMQP broker;
initiating execution of the automation test code for making Application Programming Interface calls against a distributed application for testing the distributed application;
detecting a responsive event provided by at least one distributed application node, in response to execution of the automation test code;
as the responsive event, receiving one or more messages having a specified routing key;
receiving at the queue the one or more messages having a payload that selectively indicates a nature of a state of change associated with the predetermined distributed event type; and
selectively providing the one or more messages to a requesting device having access to the queue.

### Claim 2 (depends on 1)

The method of claim 1, further comprising generating the automation test code to provide programmatic commands to at least one distributed application node from among a plurality of distributed application nodes, wherein an Application Programming Interface provides the programmatic commands.

### Claim 3 (depends on 1)

The method of claim 1, wherein detecting the responsive event identifies a resulting domain entity state change for the predetermined distributed event type.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
in response to identifying the resulting domain entity state change, generating a sequence of continuation steps in automation test code form; and
providing the sequence of continuation steps in automation test code form to the at least one distributed application node to generate a subsequent domain entity state change.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
in response to detecting the subsequent domain entity state change, provide a corresponding subsequent operation to the automation test code; and
providing a final assertion step to the automation test code in response to detecting an end of the sequence of continuation steps associated with the automation test code.

### Claim 6 (depends on 1)

The method of claim 1, further comprises generating the test context specific binding key to have properties that correspond to the automation test code and a known entity, wherein the known entity is designated by the known entity identifier.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
generating the test context specific binding key from the specified routing key having a dynamically identified component therein; and
replacing the dynamically identified component with a parameter that corresponds to a known entity associated with predetermined distributed event.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
receiving the automated test code as a series of discrete operations; and
selectively arranging the series of discrete operations to provide to the at least one distributed application node to assess at least one functional feature of the distributed application.

### Claim 9 (depends on 8)

The method of claim 8, further comprises dynamically receiving, at the queue, a responsive message associated with each event of a series of distributed events, in response to execution of the series of discrete operations.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
in response to receipt of the responsive message, providing subsequent discrete operations in automation test code form; and
generating a subsequent queue to receive subsequent messages from the established exchange.

### Claim 11

An information handling system (IHS) comprising:
a processor communicatively coupled to an advanced message queuing protocol (AMQP) message broker, and which executes a behavior driven testing module (BDTM) to enable the processor to:
receive automation test code;
generate, on an advanced message queuing protocol (AMQP) message broker, a queue for receiving the one or more messages associated with a predetermined distributed event type;
selectively generate a test context specific binding key having a known entity identifier and the specified routing key, juxtapose to generating the queue, wherein the test context specific binding key forms a bind between the queue and an established exchange associated with the AMQP broker;
initiate execution of the automation test code for making an application programming interface call against a distributed application for testing the distributed application;
detect a responsive event provided by at least one distributed application node, in response to execution of the automation test code;
as the responsive event, receive one or more messages having a specified routing key;
receive at the queue the one or more messages having a payload that selectively indicates a nature of a state of change associated with the predetermined distributed event type; and
selectively provide the one or more messages to a requesting device having access to the queue.

### Claim 12 (depends on 11)

The IHS of claim 11, further comprises generating the automation test code to provide programmatic commands to at least one distributed application node from among a plurality of distributed application nodes, wherein an Application Programming Interface provides the programmatic commands.

### Claim 13 (depends on 11)

The IHS of claim 11, wherein detection of the responsive event further comprises identifying a resulting domain entity state change for the predetermined distributed event type.

### Claim 14 (depends on 13)

The IHS of claim 13, wherein the processor:
generates a sequence of continuation steps to provide to the automation test code, in response to identifying the resulting domain entity state change; and
provides the automation test code to the at least one distributed application node to generate a subsequent domain entity state change.

### Claim 15 (depends on 14)

The IHS of claim 14, wherein the processor:
provides a corresponding subsequent operation to the automation test code, in response to detection of the subsequent domain entity state change; and
provides a final assertion step to the automation test code in response to detection of an end of the sequence of continuation steps associated with the automation test code.

### Claim 16 (depends on 11)

The IHS of claim 11, further comprises generating the test context specific binding key to have properties that correspond to the automation test code and a known entity, wherein the known entity is designated by the known entity identifier.

### Claim 17 (depends on 11)

The IHS of claim 11, wherein the processor:
generates the test context specific binding key from the specified routing key having a having a dynamically identified component therein; and
replaces the specified routing key having the dynamically identified component with a parameter that corresponds to a known entity associated with predetermined distributed event.

### Claim 18 (depends on 11)

The IHS of claim 11, wherein the processor:
receives the automated test code as a series of discrete operations; and
selectively arranges the series of discrete operations to provide to the at least one distributed application node to assess at least one functional feature of the distributed application, wherein the at least one functional feature is dynamically detected.

### Claim 19 (depends on 18)

The IHS of claim 18, wherein the processor receives, at the queue, a responsive message associated with each event of a series of distributed events, in response to execution of the series of discrete operations.

### Claim 20 (depends on 19)

The IHS of claim 19, wherein the processor:
provides subsequent discrete operations to the automated test code, in response to receipt of the responsive message; and
generate a subsequent queue to receive subsequent messages from the established exchange.
