Self-healing hybrid element identification logic

1. A computer-implemented method comprising:

evaluating, during automated test execution and using one or more processors, a first testing identifier using identification logic associated with the automated test, wherein the first testing identifier is associated with a first element of an application under test, and wherein the first testing identifier has a first type;

determining, during the automated test execution and using the one or more processors, a failure of the first testing identifier to identify, using the identification logic associated with the test, an element;

evaluating, during the automated test execution and using the one or more processors, a second testing identifier using identification logic associated with the test, the second testing identifier associated with the first element of the application under test, and wherein the second testing identifier has a second type that is different from the first type;

identifying, during the automated test execution and using the one or more processors, the first element in the application under test based on the second testing identifier; and

repairing, during the automated test execution and using the one or more processors, the first testing identifier to identify, using the identification logic associated with the automated test, the first element in the application under test.

2. The computer-implemented method of claim 1 , wherein the first testing identifier and the second testing identifier are received by recording a test session in which a user interacts with elements of the application under test.

3. The computer-implemented method of claim 2 , wherein the first testing identifier and second testing identifier are determined and suggested for use to identify the first element in the application under test during the recorded test session.

4. The computer-implemented method of claim 1 , further comprising:

generating the first testing identifier and the second testing identifier; and

recommending use of the first testing identifier and second testing identifier to identify the first element in the application under test for testing.

5. The computer-implemented method of claim 1 , further comprising:

presenting a suggested repair to a user, wherein repairing the first testing identifier is responsive to receiving user input approving the suggested repair.

6. The computer-implemented method of claim 5 , wherein the suggested repair is generated based on one or more of machine learning and a best practice.

7. The computer-implemented method of claim 1 , wherein repairing the first testing identifier does not alter a type associated with the first testing identifier.

8. The computer-implemented method of claim 1 , wherein repairing the first testing identifier alters a type associated with the first testing identifier.

9. The computer-implemented method of claim 1 , further comprising:

receiving a third testing identifier;

receiving a fourth testing identifier, a set of identifier types associated with the first and second test identifiers differing from a set of identifier types associated with the third and fourth testing identifiers;

evaluating the third testing identifier;

determining a failure of the third testing identifier to identify an element in the application under test;

evaluating the fourth testing identifier;

identifying a second element in the application under test based on the fourth testing identifier; and

repairing the third testing identifier to identify the second element in the application under test.

10. The computer-implemented method of claim 1 , wherein the first testing identifier and the second testing identifier are of a different type selected from a location-based identifier, an image-based identifier, and an attribute-based identifier.

11. A system comprising:

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the system to:

evaluate, during automated test execution, a first testing identifier using identification logic associated with the automated test, wherein the first testing identifier is associated with a first element of an application under test, and wherein the first testing identifier has a first type;

determining, during the automated test execution, a failure of the first testing identifier to identify, using the identification logic associated with the test, an element;

evaluating, during the automated test execution, a second testing identifier using identification logic associated with the test, the second testing identifier associated with the first element of the application under test, and wherein the second testing identifier has a second type that is different from the first type;

identifying, during the automated test execution, the first element in the application under test based on the second testing identifier; and

repairing, during the automated test execution, the first testing identifier to identify, using the identification logic associated with the automated test, the first element in the application under test.

12. The system of claim 11 , wherein the first testing identifier and the second testing identifier are received by recording a test session in which a user interacts with elements of the application under test.

13. The system of claim 12 , wherein the first testing identifier and second testing identifier are determined and suggested for use to identify the first element in the application under test during the recorded test session.

14. The system of claim 11 , wherein the instructions, when executed by the one or more processors, further cause the system to:

generate the first testing identifier and the second testing identifier; and

recommend use of the first testing identifier and second testing identifier to identify the first element in the application under test for testing.

15. The system of claim 11 , wherein the instructions, when executed by the one or more processors, further cause the system to:

present a suggested repair to a user, wherein repairing the first testing identifier is responsive to receiving user input approving the suggested repair.

16. The system of claim 15 , wherein the suggested repair is generated based on one or more of machine learning and a best practice.

17. The system of claim 11 , wherein repairing the first testing identifier does not alter a type associated with the first testing identifier.

18. The system of claim 11 , wherein repairing the first testing identifier alters a type associated with the first testing identifier.

19. The system of claim 11 , wherein the instructions, when executed by the one or more processors, further cause the system to:

receive a third testing identifier;

receive a fourth testing identifier, a set of identifier types associated with the first and second test identifiers differing from a set of identifier types associated with the third and fourth testing identifiers;

evaluate the third testing identifier;

determine a failure of the third testing identifier to identify an element in the application under test;

evaluate the fourth testing identifier;

identify a second element in the application under test based on the fourth testing identifier; and

repair the third testing identifier to identify the second element in the application under test.

20. The system of claim 11 , wherein the first testing identifier and the second testing identifier are of a different type selected from a location-based identifier, an image-based identifier, and an attribute-based identifier.