# US 2023/0054780 A1 · Method and device for testing microservice-based computing platforms > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2023/0054780 A1 - Document ID: US20230054780A1 - Status: Published application - Kind: A1 - Application number: 17/876,946 - Filed: 2022-07-29 - Published: 2023-02-23 - Earliest claimed: 2021-08-16 - Assignees: Amadeus S.A.S. - Applicants: Amadeus S.A.S. - Inventors: Vincent BOULINEAU; Nicolas ISCH; Serge BEUZIT - Web page: https://patentgrep.com/patent/US20230054780A1 ## CPC - G06F 11/263: Generation of test inputs, e.g. test vectors, patterns or sequences {; with adaptation of the tested hardware for testability with external testers} - G06F 11/3688: {for test execution, e.g. scheduling of test suites} - G06F 9/546: {Message passing systems or structures, e.g. queues} - G06F 2201/81: Threshold - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A computer-implemented method for testing a functionality of a computing platform, the computing platform comprising a first microservice, the method comprising: receiving, by an injector microservice, a test configuration file; determining from the test configuration file: a test input message; a test input communication mechanism; and a test output communication mechanism. The method further comprises: generating a test identifier for identifying that a message is being used for testing purposes; transmitting, by the injector microservice, the test input message to the first microservice using the test input communication mechanism, wherein the test input message comprises the test identifier; identifying, by the injector microservice, an output message transmitted via the test output communication mechanism that comprises the test identifier; and recording, by the injector microservice, the output message comprising the test identifier. ## Claims ### Claim at position 1 1-15. (canceled) ### Claim 16 A computer-implemented method for testing a functionality of a computing platform, the computing platform comprising a first microservice, the method comprising: receiving, by an injector microservice, a test configuration file; determining from the test configuration file: a test input message; a test input communication mechanism; and a test output communication mechanism; generating a test identifier for identifying that a message is being used for testing purposes; transmitting, by the injector microservice, the test input message to the first microservice using the test input communication mechanism, wherein the test input message comprises the test identifier; identifying, by the injector microservice, an output message transmitted via the test output communication mechanism that comprises the test identifier; and recording, by the injector microservice, the output message comprising the test identifier. ### Claim 17 (depends on 16) The computer-implemented method of claim 16 wherein the test input communication mechanism is a first data stream, and transmitting, by the injector microservice, the test input message comprises: generating a first data record comprising the test input message; and publishing the first data record to the first data stream. ### Claim 18 (depends on 17) The computer-implemented method of claim 17 wherein the test output communication mechanism is a second data stream, the test identifier comprises a correlation identification value, and identifying, by the injector microservice, the output message transmitted via the test output communication mechanism comprises: subscribing to the second data stream; and identifying a second data record published to the second data stream comprising the correlation identification value. ### Claim 19 (depends on 17) The computer-implemented method of claim 17 wherein the test configuration file further comprises a first limit associated with a predetermined threshold, and identifying the output message transmitted via the test output communication mechanism comprises: identifying a number of output messages transmitted via the test output communication mechanism, wherein the number of output messages is greater than or equal to one. ### Claim 20 (depends on 19) The computer-implemented method of claim 19 further comprising: determining, by the injector microservice, that the number of output messages equals the predetermined threshold; and in response to determining that the number of output messages equals the predetermined threshold, transmitting, by the injector microservice, information recorded by the injector microservice. ### Claim 21 (depends on 16) The computer-implemented method of claim 16 wherein the computing platform comprises a second microservice, and further comprising: obtaining, by the second microservice, a first message to be transmitted via the test output communication mechanism, wherein the first message is intended for a destination; determining, by the second microservice, that the first message comprises the test identifier; and in response to determining that the first message comprises the test identifier, transmitting, by the second microservice, the first message to the injector microservice. ### Claim 22 (depends on 21) The computer-implemented method of claim 21 wherein the first message is the output message, and identifying the output message transmitted via the test output communication mechanism comprises: receiving, by the injector microservice, the first message. ### Claim 23 (depends on 21) The computer-implemented method of claim 21 further comprising: determining, by the injector microservice, that the test configuration file does not comprise a mock reply associated with the destination; and in response to determining that the injector microservice does not comprise the mock reply associated with the destination, transmitting, by the injector microservice, the first message to the destination. ### Claim 24 (depends on 23) The computer-implemented method of claim 23 further comprising: determining, by the injector microservice, that the test configuration file comprises the mock reply associated with the destination; and transmitting the mock reply to the second microservice in response to determining that the test configuration file comprises the mock reply associated with the destination. ### Claim 25 (depends on 23) The computer-implemented method of claim 23 further comprising: receiving, by the injector microservice, a response message, wherein the response message is transmitted by the destination in response to receiving the first message; and transmitting, by the injector microservice to the second microservice, the response message, in response to receiving the response message transmitted by the destination. ### Claim 26 (depends on 21) The computer-implemented method of claim 21 wherein the test output communication mechanism is HTTP, the first message to be transmitted by the test output communication mechanism is a HTTP message, and the test identifier is a flag in a header of a HTTP message. ### Claim 27 (depends on 16) The computer-implemented method of claim 16, wherein the test configuration file further comprises information identifying a criteria for recording messages, the computing platform comprises a second microservice, and further comprising: obtaining, by the second microservice, a first message that is to be transmitted by the second microservice, wherein the first message is intended for a destination; determining that the first message is being used for testing purposes; in response to determining that the first message is being used for testing purposes, transmitting, by the second microservice to the injector microservice, a request for the information identifying the criteria for recording messages; transmitting, by the injector microservice, to the second microservice, a second message comprising the information identifying the criteria for recording messages; receiving, by the second microservice, the second message; determining, by the second microservice, that the first message satisfies the criteria for recording messages; and in response to determining that the first message satisfies the criteria, recording, by the second microservice, information associated with the first message. ### Claim 28 An apparatus for testing a functionality of a computing platform, the computing platform comprises a first microservice, and the apparatus comprising: an injector microservice, the injector microservice configured to: receive a test configuration file; determine from the test configuration file: a test input message; a test input communication mechanism; and a test output communication mechanism; generate a test identifier for identifying that a first message is being used for testing purposes; transmit the test input message to the first microservice using the test input communication mechanism, wherein the test input message comprises the test identifier; identify an output message transmitted via the test output communication mechanism that comprises the test identifier; and record the output message comprising the test identifier. ### Claim 29 (depends on 28) The apparatus of claim 28 wherein the test output communication mechanism is a data stream, the test identifier comprises a correlation identification value, and the injector microservice is further configured to: subscribe to the data stream; and identify a second data record published to the data stream comprising the correlation identification value, when identifying the output message transmitted via the test output communication mechanism. ### Claim 30 (depends on 29) The apparatus of claim 29 wherein the injector microservice is further configured to: receive a second message from a second microservice, wherein the second message is intended for a destination; determine that the test configuration file does not comprise a mock reply associated with the destination; and in response to determining that the injector microservice does not comprise the mock reply associated with the destination, transmit the second message to the destination. ### Claim 31 (depends on 30) The apparatus of claim 30 wherein the injector microservice is further configured to: receive a response message, wherein the response message is transmitted by the destination in response to receiving the second message; and in response to receiving the response message, transmit the response message to the second microservice. ### Claim 32 A computer program product comprising: a non-transitory computer-readable storage medium including program code instructions for testing a functionality of a computing platform, wherein the program code instructions comprise: receive a test configuration file; determine from the test configuration file: a test input message; a test input communication mechanism; and a test output communication mechanism; generate a test identifier for identifying that a message is being used for testing purposes; transmit the test input message to a microservice of the computing platform using the test input communication mechanism, wherein the test input message comprises the test identifier; identify an output message transmitted via the test output communication mechanism that comprises the test identifier; and record the output message comprising the test identifier.