Enhanced resiliency testing by enabling state level control for request
View Patent ↗A computer implemented method for testing the resiliency of a software application. The computer implemented method can test the resiliency of a software application by monitoring the program state of the software application and trigger a shutdown request when the specified program state has been reached. The shutdown request can be transmitted to the application software and executed to shut down one or more functionalities of the software application. In some examples, the method can specify the functionality to shut down and the program state which the shutdown occurs can be specified in an application configuration file.
1. A computer-implemented method for testing the resiliency of a software application, comprising:
receiving, by a processor, a configuration setting associated with the software application;
monitoring, by the processor, execution of an application request by the software application, the application request containing instructions that when executed, navigate the software application through a plurality of program states;
determining, by the processor, that a functionality of the software application is to be shut down at a program state from the plurality of program states based on the configuration setting;
detecting, by the processor, that the execution of the software application has reached the program state;
pausing, by the processor, execution of the application request; and
initiating, by the processor, a shutdown request to shut down the functionality in response to the detection.
2. The computer-implemented method of claim 1 , further comprising:
receiving, by the processor, another configuration setting associated with the application;
identifying, by the processor and based on the another configuration setting, a resume-after period specifying a period of time after which the functionality of the software application is to resume; and
initiating, by the processor, a resume request to restore the functionality when the period of time has passed after shutting down the functionality.
3. The computer-implemented method of claim 1 , wherein the program state is associated with at least one code block in the software application.
4. The computer-implemented method of claim 1 , wherein the functionality was created through one of the plurality of program states.
5. The computer-implemented method of claim 1 , wherein the program state is one of cloning a template, configuring a network setting, configuring a CPU setting, configuring a guest Operating System setting, and powering on a VM.
6. The computer-implemented method of claim 1 , further comprising resuming, by the processor, execution of the application request.
7. The computer-implemented method of claim 1 , further comprising monitoring, by the processor, a result generated from the shutdown request.
8. One or more non-transitory computer readable storage devices containing instructions, that when executed, control a computer system to be configured for:
receiving a configuration setting associated with the software application;
monitoring execution of an application request by the software application, the application request containing instructions that when executed, navigate the software application through a plurality of program states;
determining that a functionality of the software application is to be shut down at a program state from the plurality of program states based on the configuration setting;
detecting that the execution of the software application has reached the program state;
pausing execution of the application request; and
initiating a shutdown request to shut down the functionality in response to the detection.
9. The one or more non-transitory computer readable storage devices of claim 8 , further comprising:
receiving another configuration setting associated with the application;
identifying, based on the another configuration setting, a resume-after period specifying a period of time after which the functionality of the software application is to resume; and
initiating a resume request to restore the functionality when the period of time has passed after shutting down the functionality.
10. The one or more non-transitory computer readable storage devices of claim 8 , wherein the program state is associated with at least one code block in the software application.
11. The one or more non-transitory computer readable storage devices of claim 8 , wherein the functionality was created through one of the plurality of program states.
12. The one or more non-transitory computer readable storage devices of claim 8 , wherein the program state is one of cloning a template, configuring a network setting, configuring a CPU setting, configuring a guest Operating System setting, and powering on a VM.
13. The one or more non-transitory computer readable storage devices of claim 8 , further comprising resuming execution of the application request.
14. The one or more non-transitory computer readable storage devices of claim 8 , further comprising monitoring a result generated from the shutdown request.
15. An apparatus, comprising:
one or more computer processors; and
one or more non-transitory computer-readable storage devices comprising instructions, that when executed, control the one or more computer processors to be configured for:
receiving a configuration setting associated with the software application;
monitoring execution of an application request by the software application, the application request containing instructions that when executed, navigate the software application through a plurality of program states;
determining that a functionality of the software application is to be shut down at a program state from the plurality of program states based on the configuration setting;
detecting that the execution of the software application has reached the program state;
pausing execution of the application request; and
initiating a shutdown request to shut down the functionality in response to the detection.
16. The apparatus of claim 15 , further comprising:
receiving another configuration setting associated with the application;
identifying, based on the another configuration setting, a resume-after period specifying a period of time after which the functionality of the software application is to resume; and
initiating a resume request to restore the functionality when the period of time has passed after shutting down the functionality.
17. The apparatus of claim 15 , wherein the program state is associated with at least one code block in the software application.
18. The apparatus of claim 15 , wherein the functionality was created through one of the plurality of program states.
19. The apparatus of claim 15 , wherein the program state is one of cloning a template, configuring a network setting, configuring a CPU setting, configuring a guest Operating System setting, and powering on a VM.
20. The apparatus of claim 15 , further comprising resuming execution of the application request.