Prioritizing resiliency tests of microservices

• US 10,169,220 B2
• Filed: 08/05/2016
• Issued: 01/01/2019
• Est. Priority Date: 08/05/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Rajagopalan, Shriram, Sinha, Saurabh
• Primary Examiner(s): Mehrmanesh, Elmira
• Application Number:
  US15/229,958
• Publication Number:
  US 20180039570A1
• Time in Patent Office: 879 Days
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3676 for coverage analysis
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

Techniques for automated resiliency testing systems are provided. In one example, a computer-implemented method comprises traversing, by a system operatively coupled to a processor, an application program interface call subgraph of a microservices-based application in a depth first traversal. The computer-implemented method also comprises, during the traversing, performing, by the system, resiliency testing of parent application program interfaces of the application program interface call subgraph according to a systematic resilience testing algorithm that reduces and/or eliminates redundant resiliency testing of parent application program interfaces.

Claims

1. A system, comprising:

a memory that stores computer executable components; and

a processor that executes the computer executable components stored in the memory, wherein the computer executable components comprise;

a test execution component that;

traverses an application program interface call subgraph of a microservices-based application in a depth first traversal pattern; and

during the traversal, performs resiliency testing of parent application program interfaces of the application program interface call subgraph according to a systematic resilience testing algorithm that reduces redundant resiliency testing of parent application program interfaces, the systematic resilience testing algorithm comprising;

during the traversal at a stop at a parent application program interface of the application program interface call subgraph;

in response to the parent application program interface having multiple dependent application program interfaces, calls to all direct and indirect dependent application program interfaces of the parent application program interface annotated as having been bounded retry pattern tested and circuit breaker pattern tested, and the parent application program interface not being annotated as having been bulkhead pattern tested, perform a bulkhead pattern test on the parent application program interface and annotate the parent application program interface as bulkhead pattern tested.

2. The system of claim 1, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph for a current dependent application program interface parent application program interface in the depth first traversal pattern;

performance of a bounded retry pattern test on the parent application program interface for a call to the current dependent application program interface of the parent application program interface in the depth first traversal pattern; and

in response to the bounded retry pattern test on the parent application program interface passing, annotation of the parent application program interface as having been bounded retry pattern tested for the dependent application program interface to which the bounded retry pattern test was performed.

3. The system of claim 1, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph, and for a current dependent application program interface parent application program interface in the depth first traversal pattern;

performance of a circuit breaker pattern test on the parent application program interface for a call to the current dependent application program interface of the parent application program interface in the depth first traversal pattern; and

in response to the circuit breaker pattern test on the parent application program interface passing, annotation of the parent application program interface as having been circuit breaker pattern tested for the current dependent application program interface to which the circuit breaker pattern test was performed.

4. The system of claim 3, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph;

in response to the parent application program interface having multiple dependent application program interfaces, and calls to all direct and indirect dependent application program interfaces of the parent application program interface are not annotated as having been bounded retry pattern tested and circuit breaker retry pattern tested, skip performance of the bulkhead pattern test on the parent application program interface.

5. The system of claim 1, wherein the systematic resilience testing algorithm further comprises:

based on at least one resiliency test pattern, generation of at least one failure scenario for the application program interface call subgraph of subset; and

using the at least one failure scenario, test of the application program interface call subgraph for the at least one resiliency test pattern.

6. The system of claim 5, wherein the at least one resiliency test pattern is selected from the group consisting of a timeout pattern, a bounded retry pattern, a circuit breaker pattern, and a bulkhead pattern.

7. The system of claim 1, wherein the test execution component transmits a recommendation to at least one recipient entity indicating whether to deploy the microservices-based application in a live environment, and wherein the recommendation is determined based on an analysis of results of the resiliency testing.

8. A computer-implemented method, comprising:

traversing, by a system operatively coupled to a processor, an application program interface call subgraph of a microservices-based application in a depth first traversal pattern; and

during the traversing, performing, by the system, resiliency testing of parent application program interfaces of the application program interface call subgraph according to a systematic resilience testing algorithm that reduces redundant resiliency testing of parent application program interfaces, the systematic resilience testing algorithm comprising;

during the traversal at a stop at a parent application program interface of the application program interface call subgraph;

in response to the parent application program interface having multiple dependent application program interfaces, calls to all direct and indirect dependent application program interfaces of the parent application program interface marked as having been bounded retry pattern tested and circuit breaker pattern tested, and the parent application program interface not being marked as bulkhead pattern tested, performing a bulkhead pattern test on the parent application program interface and marking the parent application program interface as bulkhead pattern tested.

9. The computer-implemented method of claim 8, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph for a current dependent application program interface parent application program interface in the depth first traversal pattern;

performing a bounded retry pattern test on the parent application program interface for a call to the current dependent application program interface of the parent application program interface in the depth first traversal pattern; and

in response to the bounded retry pattern test on the parent application program interface passing, marking the parent application program interface as having been bounded retry pattern tested for the dependent application program interface to which the bounded retry pattern test was performed.

10. The computer-implemented method of claim 8, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph for a current dependent application program interface parent application program interface in the depth first traversal pattern;

performing a circuit breaker pattern test on the parent application program interface for a call to the current dependent application program interface of the parent application program interface in the depth first traversal pattern; and

in response to the circuit breaker pattern test on the parent application program interface passing, marking the parent application program interface as having been circuit breaker pattern tested for the dependent application program interface to which the circuit breaker pattern test was performed.

11. The computer-implemented method of claim 8, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph;

in response to the parent application program interface having multiple dependent application program interfaces, calls to all direct and indirect dependent application program interfaces of the parent application program interface are not marked as having been bounded retry pattern tested and circuit breaker retry pattern tested, skip performing a bulkhead pattern test on the parent application program interface.

12. The computer-implemented method of claim 8, wherein the systematic resilience testing algorithm further comprises:

generating, by the system based on at least one resiliency test pattern, at least one failure scenario for the application program interface call subgraph of subset; and

testing, by the system, the application program interface call subgraph for the at least one resiliency test pattern using the at least one failure scenario.

13. The computer-implemented method of claim 12, wherein the at least one resiliency test pattern is selected from the group consisting of a timeout pattern, a bounded retry pattern, a circuit breaker pattern, and a bulkhead pattern.

14. The computer-implemented method of claim 8, further comprising providing a recommendation to at least one recipient indicating whether to deploy the microservices-based application in a live environment, and wherein the recommendation is determined based on an analysis of results of the resiliency testing.

15. A computer program product for performing resiliency testing of application program interface call subgraph associated with a user interface of a microservices-based application, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processing component to cause the processing component to:

traverse an application program interface call subgraph of a microservices-based application in a depth first traversal pattern; and

during the traversal, perform resiliency testing of parent application program interfaces of the application program interface call subgraph according to a systematic resilience testing algorithm that reduces redundant resiliency testing of parent application program interfaces, the systematic resilience testing algorithm comprises;

during the traversal at a stop at a parent application program interface of the application program interface call subgraph;

in response to the parent application program interface having multiple dependent application program interfaces, calls to all direct and indirect dependent application program interfaces of the parent application program interface not marked as having been bounded retry pattern tested and circuit breaker retry pattern tested, and the parent application program interface failing to have been marked as bulkhead pattern tested, performing a bulkhead pattern test on the parent application program interface and marking the parent application program interface as bulkhead pattern tested.

16. The computer program product of claim 15, wherein the systematic resilience testing algorithm further comprises:

during the traversal at stop at parent application program interface of the application program interface call subgraph for a current dependent application program interface parent application program interface in the depth first traversal pattern;

performance of a bounded retry pattern test on the parent application program interface for a call to the current dependent application program interface of the parent application program interface in the depth first traversal pattern; and

in response to the bounded retry pattern test on the parent application program interface passing, marking of the parent application program interface as having been bounded retry pattern tested for the dependent application program interface to which the bounded retry pattern test was performed.

17. The computer program product of claim 15, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph for a current dependent application program interface parent application program interface in the depth first traversal pattern;

performance of a circuit breaker pattern test on the parent application program interface for a call to the current dependent application program interface of the parent application program interface in the depth first traversal pattern; and

in response to the circuit breaker pattern test on the parent application program interface passing, marking of the parent application program interface as having been circuit breaker pattern tested for the dependent application program interface to which the circuit breaker pattern test was performed.

18. The computer program product of claim 15, wherein the systematic resilience testing algorithm further comprises:

during the traversal at the stop at the parent application program interface of the application program interface call subgraph;

in response to the parent application program interface having multiple dependent application program interfaces, calls to all direct and indirect dependent application program interfaces of the parent application program interface are not marked as having been bounded retry pattern tested and circuit breaker retry pattern tested, skip performance of a bulkhead pattern test on the parent application program interface.

19. The computer program product of claim 15, wherein the systematic resilience testing algorithm further comprises:

generation of, based on at least one resiliency test pattern, at least one failure scenario for the application program interface call subgraph; and

test of the application program interface call subgraph for the at least one resiliency test pattern using the at least one failure scenario.

20. The computer program product of claim 19, wherein the at least one resiliency test pattern is selected from the group consisting of a timeout pattern, a bounded retry pattern, a circuit breaker pattern, and a bulkhead pattern.