Systems and methods for automated test data microservices

Patent metadata

Field	Value
Publication number	US-11520688-B1
Application number	US-202017032186-A
Country	US
Kind code	B1
Filing date	Sep 25, 2020
Priority date	Sep 25, 2020
Publication date	Dec 6, 2022
Grant date	Dec 6, 2022

Abstract

Systems and methods for automated test data microservices are provided. Test versions of software (such as an Application Programming Interface (API)) may be configured to automatically generate test data and to call a microservice to manage the test data. The microservice may automatically add and remove the test data from an operational data store to facilitate the testing process and to automatically perform setup and teardown stages of the testing process.

First claim

What is claimed is:

1. A system for shared API test data microservices operating in a shared testing environment, comprising:
an electronic processing device; and
a non-transitory data storage device in communication with the electronic processing device, the non-transitory data storage device storing (i) a test version of a first API, (ii) a test version of a second API, and (iii) instructions defining an API test data microservice, wherein an execution by the electronic processing device results in:
generating, by the test version of the first API, first API test data, wherein the first API test data comprises a first call to the API test data microservice;
initiating an execution of the test version of the first API utilizing the first API test data, wherein the initiating comprises executing the first call to the API test data microservice;
adding, automatically by the API test data microservice and in response to the executed first call to the first API test data microservice, a first plurality of test data elements from the first API test data to a shared test environment data store;
storing, by the API test data microservice and for each test data element of the first plurality of test data elements from the first API test data that are added to the shared test environment data store, a unique test data element identifier;
continuing an execution of the test version of the first API utilizing the first plurality of test data elements from the first API test data that are added to the shared test environment data store;
concluding the execution of the test version of the first API; and
removing, automatically by the API test data microservice, in response to the concluding, and utilizing the unique test data element identifiers for the first plurality of test data elements from the first API test data that are added to the shared test environment data store, the first plurality of test data elements from the first API test data from the shared test environment data store.

2. The system of claim 1 , wherein the execution by the electronic processing device, further results in:
receiving, from a programmer device in communication with the electronic processing device, data defining the test version of the first API.

3. The system of claim 1 , wherein the execution by the electronic processing device, further results in:
passing, by the API test data microservice and to the test version of the first API, and in response to an indication of the executed first call to the API test data microservice, unique test data element identifiers for the first plurality of test data elements from the first API test data that are added to the shared test environment data store.

4. The system of claim 1 , wherein the first call to the API test data microservice comprises an identification of the shared test environment data store from a listing of a plurality of available shared test environment data stores.

5. The system of claim 1 , wherein the first call to the API test data microservice comprises an identification of an address of the shared test environment data store.

6. The system of claim 5 , wherein the first call to the API test data microservice comprises an identification of an address of a specific location within the shared test environment data store.

7. The system of claim 1 , wherein the shared test environment data store comprises a database.

8. The system of claim 1 , wherein the shared test environment data store comprises a message queue.

9. The system of claim 1 , wherein the API test data microservice comprises a RESTful API.

10. The system of claim 1 , wherein the first API test data comprises a second call to the API test data microservice and wherein the concluding of the execution of the test version of the first API comprises executing the second call to the API test data microservice.

11. The system of claim 10 , wherein the second call to the API test data microservice defines a request to conduct the removing.

12. The system of claim 11 , wherein the request to conduct the removing comprises an indication of the unique test data element identifiers for the first plurality of test data elements from the first API test data that are added to the shared test environment data store.

13. The system of claim 1 , wherein the first API test data comprises a message in a message queue.

14. The system of claim 1 , wherein the first API test data comprises simulated credit card transaction data.

15. The system of claim 1 , wherein the first API test data comprises a flat file.

16. The system of claim 1 , wherein the execution by the electronic processing device, further results in:
generating, by the test version of the second API, second API test data, wherein the second API test data comprises a second call to the API test data microservice;
initiating an execution of the test version of the second API utilizing the second API test data, wherein the initiating comprises executing the second call to the API test data microservice;
adding, automatically by the API test data microservice and in response to the executed second call to the API test data microservice, a second plurality of test data elements from the second API test data to the shared test environment data store;
storing, by the API test data microservice and for each test data element of the second plurality of test data elements from the second API test data that are added to the shared test environment data store, a unique test data element identifier;
continuing an execution of the test version of the second API utilizing the second plurality of test data elements from the second API test data that are added to the shared test environment data store;
concluding the execution of the test version of the second API; and
removing, automatically by the API test data microservice, in response to the concluding of the execution of the test version of the second API, and utilizing the unique test data element identifiers for the second plurality of test data elements from the second API test data that are added to the shared test environment data store, the second plurality of test data elements from the second API test data from the shared test environment data store.

Assignees

• Travelers Indemnity Co

Inventors

• Poirier Michael J

Classifications

• G06F11/3688 Primary

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

• G06F11/3692

  for test results analysis · CPC title

• G06F11/3696

  Methods or tools to render software testable · CPC title

• G06F11/3684 Primary

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

• G06F11/368

  for test version control, e.g. updating test cases to a new software version · CPC title