Method and system for automatically testing event-driven microservices

Patent metadata

Field	Value
Publication number	US-2022019520-A1
Application number	US-202016929529-A
Country	US
Kind code	A1
Filing date	Jul 15, 2020
Priority date	Jul 15, 2020
Publication date	Jan 20, 2022
Grant date	—

Abstract

A method for facilitating automated testing of event-driven microservices is provided. The method includes receiving a scenario that includes a set of instructions to test a microservice; automatically generating, based on the scenario, a production event relating to an action to be performed and a consumption event relating to a record of the performed action; automatically generating a first test event using the production event; outputting the first test event to the microservice; automatically retrieving a first result relating to the execution of the first test event by the microservice by using the consumption event; and validating the first result based on the scenario. The method further includes displaying the first result and a notification on a graphical user interface based on an outcome of the validating.

First claim

1 . A method for facilitating automated testing of event-driven microservices, the method being implemented by at least one processor, the method comprising:
receiving, by the at least one processor, at least one scenario that includes at least one set of instructions to test at least one microservice; automatically generating, by the at least one processor based on the at least one scenario, at least one production event relating to at least one action to be performed and at least one consumption event relating to at least one record of the performed action; automatically generating, by the at least one processor using the at least one production event, at least one first test event; identifying, by the at least one processor, the at least one microservice in a choreography of multiple event-driven microservices by using the generated at least one production event: outputting, by the at least one processor, the at least one first test event to the at least one microservice based on a result of the identifying; automatically retrieving, by the at least one processor using the at least one consumption event, at least one first result relating to the execution of the at least one first test event by the at least one microservice, the at least one first result including information that corresponds to the multiple event-driven microservices in the choreography; validating, by the at least one processor, the at least one first result based on the at least one scenario; and extrapolating, by the at least one processor, dependency data and interaction data for each of the multiple event-driven microservices in the choreography by using the information in the at least one first result.

2 . The method of claim 1 , further comprising displaying, via a graphical user interface, the at least one first result and at least one notification based on an outcome of the validating.

3 . The method of claim 1 , further comprising displaying, via a graphical user interface, a choreography of the at least one microservice that is generated based on the at least one first result, the choreography including derived dependencies and interactions between the at least one microservice and other microservices.

4 . The method of claim 1 , further comprising:
automatically generating, by the at least one processor using the at least one production event, at least one second test event based on a predetermined schedule; outputting, by the at least one processor, the at least one second test event to the at least one microservice; automatically retrieving, by the at least one processor using the at least one consumption event, at least one second result relating to the execution of the at least one second test event by the at least one microservice; and validating, by the at least one processor, the at least one second result based on the at least one scenario.

5 . The method of claim 4 , further comprising:
storing, by the at least one processor, an outcome of the validating in a log corresponding to the at least one scenario; and displaying, by the at least one processor via a graphical user interface, the log.

6 . The method of claim 4 , wherein the predetermined schedule includes at least one from among an intermittent schedule and a periodic schedule.

7 . The method of claim 1 , further comprising:
automatically generating, by the at least one processor using the at least one production event, a plurality of third test events; outputting, by the at least one processor, the plurality of third test events to the at least one microservice; retrieving, by the at least one processor, a measurement of at least one parameter relating to performance of the at least one microservice; and storing, by the at least one processor in a memory, the measurement in an electronic document corresponding to the at least one scenario.

8 . The method of claim 7 , wherein the at least one first result and the measurement are displayed on a graphical user interface.

9 . The method of claim 1 , wherein the at least one scenario includes at least one operational situation to test the at least one microservice, the operational situation including a postulated sequence of procedures for the at least one microservice.

10 . The method of claim 1 , wherein the at least one scenario is received via at least one from among a hypertext transfer protocol and an application programing interface.

11 . A computing device configured to implement an execution of a method for facilitating automated testing of event-driven microservices, the computing device comprising:
a processor; a memory; and a communication interface coupled to each of the processor and the memory, wherein the processor is configured to:
receive at least one scenario that includes at least one set of instructions to test at least one microservice;
automatically generate, based on the at least one scenario, at least one production event relating to at least one action to be performed and at least one consumption event relating to at least one record of the performed action;
automatically generate, by using the at least one production event, at least one first test event;
identify the at least one microservice in a choreography of multiple event-driven microservices by using the generated at least one production event:
output the at least one first test event to the at least one microservice based on a result of the identifying;
automatically retrieve, by using the at least one consumption event, at least one first result relating to the execution of the at least one first test event by the at least one microservice, the at least one first result including information that corresponds to the multiple event-driven microservices in the choreography;
validate the at least one first result based on the at least one scenario; and
extrapolate dependency data and interaction data for each of the multiple event-driven microservices in the choreography by using the information in the at least one first result.

12 . The computing device of claim 11 , wherein the processor is further configured to display, via a graphical user interface, the at least one first result and at least one notification based on an outcome of the validating.

13 . The computing device of claim 11 , wherein the processor is further configured to display, via a graphical user interface, at least one visualization relating to a choreography of the at least one microservice based on the at least one first result, the choreography including derived dependencies and interactions between the at least one microservice and other microservices.

14 . The computing device of claim 11 , wherein the processor is further configured to:
automatically generate, by using the at least one production event, at least one second test event based on a predetermined schedule; output the at least one second test event to the at least one microservice; automatically retrieve, by using the at least one consumption event, at least one second result relating to the execution of the at least one second test event by the at least one microservice; and validate the at least one second result based on the at least one scenario.

15 . The computing device of claim 14 , wherein the processor is further configured to:
store an outcome of the validating in a log corresponding to the at least one scenario; and display, via a graphical user interface, the log.

16 . The computing device of claim 14 , wherein the predetermined schedule includes at least one from among an intermittent schedule and a periodi

Assignees

• Jpmorgan Chase Bank Na

Inventors

• Katdare Amol R
• Tinker Michael

Classifications

• G06F11/3698

  Environments for analysis, debugging or testing of software · CPC title

• G06F11/3688 Primary

  for test execution, e.g. scheduling of test suites · CPC title

• G06F11/3684 Primary

  for test design, e.g. generating new test cases · CPC title

• G06F11/3692

  for test results analysis · CPC title

• G06F11/3409

  for performance assessment · CPC title