Method for automated integration testing with mock microservices

Patent metadata

Field	Value
Publication number	US-10592403-B2
Application number	US-201715841428-A
Country	US
Kind code	B2
Filing date	Dec 14, 2017
Priority date	Nov 20, 2017
Publication date	Mar 17, 2020
Grant date	Mar 17, 2020

Abstract

A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

First claim

What is claimed is:

1. A method for automated integration testing with mock microservices, the method comprising:
accepting from an automated application-testing system, by a processor, a request to perform an integration test upon a tested set of microservices, where the tested set of microservices is comprised by a tested application;
launching, by the processor, a mock server;
directing, by the processor, the mock server to launch and maintain a mock entity,
where the mock entity emulates an operation of a software entity that is not a subject of the integration test, and
where the software entity is known to interact with at least one microservice of the set of microservices in a production environment;

receiving, by the processor, from the mock server a first service request that had been communicated to the mock entity by the tested set;
sending, to the tested set, by the processor, in response to the receiving, a service response to a most recently received service request, where the sending comprises communicating the service response to the mock server and the mock server directing the mock entity to forward the service response to the tested set;
receiving, by the processor, an additional service request, where the additional service request is received at a time later than a time of the receipt of the first service request;
repeating, by the processor, the sending in response to the processor receiving the additional service request;
determining, by the processor, from the receiving of the additional service request, that the test set is operating correctly; and
returning, by the processor, to the automated application-testing system a notification that the tested set has passed the integration test.

2. The method of claim 1 ,
where the tested set comprises all microservices of the tested application,
where each microservice of the all microservices functions independently of any other microservice of the all microservices, and
where the mock entity emulates a software entity that is capable of communicating with the tested application.

3. The method of claim 1 ,
where the mock entity emulates an untested microservice of the tested application,
where the untested microservice is a microservice that is not comprised by the tested set, and
where the untested microservice is capable of communicating with a tested microservice of the tested set.

4. The method of claim 1 , where the processor communicates with the mock server through a messaging system.

5. The method of claim 4 , where the messaging system is a publish-subscribe system.

6. The method of claim 1 ,
where the automated application-testing system comprises a behavior store, and
where each service response sent by the processor to the mock server is selected as a function of contents of the behavior store.

7. The method of claim 6 ,
where the automated application-testing system further comprises a test script, and
where the processor dynamically updates the contents of the behavior store during the integration test as a function of the test script.

8. The method of claim 7 , where the dynamic updating is performed as a further function of a current state of the tested set.

9. The method of claim 7 , where the dynamic updating is performed in response to communications received from the tested set.

10. The method of claim 1 , further comprising providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable program code in the computer system, wherein the computer-readable program code in combination with the computer system is configured to implement the accepting, the launching, the directing, the receiving, the sending, the repeating, the determining, and the returning.

Assignees

• IBM

Inventors

• Reeve John A
• Frost Mark Peter
• Thorpe Paul S M

Classifications

• G06F17/17

  Function evaluation by approximation methods, e.g. inter- or extrapolation, smoothing, least mean square method ({G06F17/18 takes precedence } ; interpolation for numerical control G05B19/18) · CPC title

• G06F11/3692

  for test results analysis · CPC title

• G06F11/3684

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

• G06F11/3696 Primary

  Methods or tools to render software testable · CPC title

• G06F11/36

  Prevention of errors by analysis, debugging or testing of software · CPC title