System for automated error analysis in an application testing environment using robotic process automation

1. A system for automated error analysis in an application testing environment using robotic process automation, the system comprising:

at least one non-transitory storage device; and

at least one processing device coupled to the at least one non-transitory storage device, wherein the at least one processing device is configured to:

electronically receive one or more exceptions from one or more automated test scripts;

determine one or more exception types associated with the one or more exceptions; and

initiate an exception handling bot configured to handle the one or more exceptions based on at least the one or more exception types, wherein handling further comprises:

determining one or more exception handling routines associated with the one or more exception types from a knowledge management database;

retrieving, from the knowledge management database, at least one of the one or more exception handling routines; and

initiating an execution of the at least one of the one or more exception handling routines to handle the one or more exceptions.

2. The system of claim 1 , wherein the at least one processing device is further configured to:

generate an ad-hoc exception handling routine based on at least the one or more exception types.

3. The system of claim 2 , wherein the at least one processing device is further configured to:

determine a pre-configured subroutine structure associated with the one or more exception types;

receive information associated with the one or more exceptions, wherein the information associated with the one or more exceptions comprises one or more automated test script subroutines that have failed due to one or more application environment issues;

receive information associated with the one or more automated test scripts, wherein the information associated with the one or more automated test scripts further comprises information associated with one or more application components being tested by the one or more automated test scripts;

generate the ad-hoc exception handling routine based on at least the pre-configured subroutine structure, the information associated with the one or more exceptions, and the information associated with the one or more automated test scripts; and

transmit control signals configured to cause the exception handling bot to execute the ad-hoc exception handling routine to handle the one or more exceptions.

4. The system of claim 1 , wherein the at least one processing device is further configured to:

update the knowledge management database with the one or more exceptions received from the one or more automated test scripts based on at least the one or more exception types.

5. The system of claim 1 , wherein the knowledge management database comprises one or more exception handling routines associated with each of the one or more exception types.

6. The system of claim 1 , wherein the at least one processing device is further configured to:

determine whether the one or more exceptions have been resolved based on at least executing, using the exception handling bot, the at least one of the one or more exception handling routines to handle the exception; and

re-execute the one or more automated test scripts based on at least determining that the one or more exceptions have been resolved.

7. The system of claim 1 , wherein the at least one processing device is further configured to:

implement one or more machine learning algorithms on one or more training examples, wherein the one or more training examples comprises one or more inputs and a supervisory signal, wherein the one or more inputs comprises at least one or more historical exceptions, wherein the supervisory signal comprises the one or more exception types; and

generate an inferred function based on at least implementing the one or more machine learning algorithms on the one or more training examples to classify one or more new observations, wherein the one or more new observations comprises the one or more exceptions.

8. The system of claim 7 , wherein the at least one processing device is further configured to:

electronically receive the one or more exceptions;

classify, using the inferred function, the one or more exceptions into at least one of the one or more exception types; and

determine at least one of the one or more exception handling routines based on at least classifying the one or more exceptions into at least one of the one or more exception types.

9. The system of claim 7 , wherein the at least one processing device is further configured to:

determine that at least one of the one or more exceptions were not classified into at least one of the one or more exception types;

transmit a control signal configured to initiate a user interface for display on a user device, wherein the user interface comprises information associated with the at least one of the one or more exceptions that were not classified into at least one of the one or more exception types;

receive, via the user interface, a user input comprising one or more actions to resolve the at least one of the one or more exceptions;

determine that the one or more actions resolves the at least one of the one or more exceptions; and

re-execute the one or more automated test scripts based on at least determining that the at least one of the one or more exceptions have been resolved.

10. A computer implemented method for automated error analysis in an application testing environment using robotic process automation, the method comprising:

electronically receiving one or more exceptions from one or more automated test scripts;

determining one or more exception types associated with the one or more exception; and

initiating an exception handling bot configured to handle the one or more exceptions based on at least the one or more exception types, wherein handling further comprises:

determining one or more exception handling routines associated with the one or more exception types from a knowledge management database;

retrieving, from the knowledge management database, at least one of the one or more exception handling routines; and

initiating an execution of the at least one of the one or more exception handling routines to handle the one or more exceptions.

11. The method of claim 10 , wherein the method further comprises generating, using the exception handling bot, an ad-hoc exception handling routine based on at least the one or more exception types.

12. The method of claim 11 , wherein generating the ad-hoc exception handling routine further comprises:

determining a pre-configured subroutine structure associated with the one or more exception types;

receiving information associated with the one or more exceptions, wherein the information associated with the one or more exceptions comprises one or more automated test script subroutines that have failed due to one or more application environment issues;

receiving information associated with the one or more automated test scripts, wherein the information associated with the one or more automated test scripts further comprises information associated with one or more application components being tested by the one or more automated test scripts;

generating the ad-hoc exception handling routine based on at least the pre-configured subroutine structure, the information associated with the one or more exceptions, and the information associated with the one or more automated test scripts; and

transmitting control signals configured to cause the exception handling bot to execute the ad-hoc exception handling routine to handle the one or more exceptions.

13. The method of claim 10 , wherein the method further comprises updating the knowledge management database with the one or more exceptions received from the one or more automated test scripts based on at least the one or more exception types.

14. The method of claim 10 , wherein the method further comprises:

determining whether the one or more exceptions have been resolved based on at least executing, using the exception handling bot, the at least one of the one or more exception handling routines to handle the exception; and

re-executing the one or more automated test scripts based on at least determining that the one or more exceptions have been resolved.

15. The method of claim 10 , wherein the method further comprises:

implementing one or more machine learning algorithms on one or more training examples, wherein the one or more training examples comprises one or more inputs and a supervisory signal, wherein the one or more inputs comprises at least one or more historical exceptions, wherein the supervisory signal comprises the one or more exception types; and

generating an inferred function based on at least implementing the one or more machine learning algorithms on the one or more training examples to classify one or more new observations, wherein the one or more new observations comprises the one or more exceptions.

16. The method of claim 15 , wherein the method further comprises:

electronically receiving the one or more exceptions;

classifying, using the inferred function, the one or more exceptions into at least one of the one or more exception types; and

determining at least one of the one or more exception handling routines based on at least classifying the one or more exceptions into at least one of the one or more exception types.

17. The method of claim 15 , wherein the method further comprises:

determining that at least one of the one or more exceptions were not classified into at least one of the one or more exception types; and

transmitting a control signal configured to initiate a user interface for display on a user device, wherein the user interface comprises information associated with the at least one of the one or more exceptions that were not classified into at least one of the one or more exception types; and

receiving, via the user interface, a user input comprising one or more actions to resolve the at least one of the one or more exceptions;

determining that the one or more actions resolves the at least one of the one or more exceptions; and

re-executing the one or more automated test scripts based on at least determining that the at least one of the one or more exceptions have been resolved.

18. A computer program product for automated error analysis in an application testing environment using robotic process automation, the computer program product comprising a non-transitory computer-readable medium comprising code causing a first apparatus to:

electronically receive one or more exceptions from one or more automated test scripts;

determine one or more exception types associated with the one or more exceptions;

initiate an exception handling bot configured to handle the one or more exceptions based on at least the one or more exception types, wherein handling further comprises:

determining one or more exception handling routines associated with the one or more exception types from a knowledge management database;

retrieving, from the knowledge management database, at least one of the one or more exception handling routines; and

initiating an execution of the at least one of the one or more exception handling routines to handle the one or more exceptions.

19. The computer program product of claim 18 , wherein the first apparatus is further configured to generate an ad-hoc exception handling routine based on at least the one or more exception types.

20. The computer program product of claim 19 , wherein generating the ad-hoc exception handling routine further comprises:

determine a pre-configured subroutine structure associated with the one or more exception types;

receive information associated with the one or more exceptions, wherein the information associated with the one or more exceptions comprises one or more automated test script subroutines that have failed due to one or more application environment issues;

receive information associated with the one or more automated test scripts, wherein the information associated with the one or more automated test scripts further comprises information associated with one or more application components being tested by the one or more automated test scripts;

generate the ad-hoc exception handling routine based on at least the pre-configured subroutine structure, the information associated with the one or more exceptions, and the information associated with the one or more automated test scripts; and

transmit control signals configured to cause the exception handling bot to execute the ad-hoc exception handling routine to handle the one or more exceptions.