Automated Extensible User Interface Testing

• US 20070294586A1
• Filed: 05/31/2006
• Published: 12/20/2007
• Est. Priority Date: 05/31/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Parvathy, Ganesh Sankarakumar, Yu, Jin, Patil, Dipti A.
• Granted Patent: US 7,529,977 B2
• Time in Patent Office: Days
• US Class Current: 714/38.14
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3672 Test management

Abstract

Automated extensible user interface testing supports testing of a user interface of a program. Test data is accessed, the test data including multiple test steps. Each test step describes at least a part of a test to be performed on the user interface. For each of the multiple test steps, one or more application program interface (API) methods to invoke to carry out the part of the test is determined. This determination is based at least in part on the test data and on an identification from the API of methods supported by the API. Each of the one or more API methods is then invoked to carry out the part of the test. Verification can be performed to ensure, for example, that specified files were created, or registry values were changed, or user interface elements appear and exist.

Claims

1. One or more computer readable media having stored thereon a plurality of instructions to test a user interface of a program, the plurality of instructions, when executed by one or more processors, causes the one or more processors to:

access test data, the test data including a plurality of test steps, each test step describing at least a part of a test to be performed on the user interface;

determine, for each of the plurality of test steps, one or more application program interface (API) methods to invoke to carry out the part of the test, the determination being based at least in part on the test data and on methods supported by the API;

invoke each of the one or more API methods to carry out the part of the test.

2. One or more computer readable media as recited in claim 1, wherein to determine one or more API methods to invoke is to, for each of the plurality of test steps:

identify one or more attributes of an operation in the test step;

identify which one or more API methods can be invoked using the identified one or more attributes; and

select one of the identified one or more API methods.

3. One or more computer readable media as recited in claim 1, wherein to determine one or more API methods to invoke is further to obtain, from the API, an identification of methods supported by the API.

4. One or more computer readable media as recited in claim 1, wherein each of the plurality of tests steps includes one or more of a Run Process operation, an Action operation, a Verify operation, a Set Property operation, a Sleep operation, a Wait For State operation, and a Registry operation.

5. One or more computer readable media as recited in claim 1, wherein the tests data includes a Run Process operation, an Action operation, a Verify operation, a Set Property operation, a Sleep operation, a Wait For State operation, and a Registry operation.

6. One or more computer readable media as recited in claim 1, wherein to invoke each of the one or more API methods is to invoke each of the one or more API methods using one or more attributes of an operation in the test step of the test data.

7. A method for testing a user interface of a program, the method comprising:

identifying a portion of a test to be performed on the user interface;

determining, based at least in part on data associated with the identified portion, which one or more of a plurality of application program interface (API) methods can be called using the data to carry out the portion of the test; and

calling at least one of the one or more API methods to carry out the portion of the test.

8. A method as recited in claim 7, wherein determining which one or more of a plurality of API methods to call comprises:

identifying one or more attributes of an operation in the portion of the test;

identifying which one or more API methods can be called using the identified one or more attributes; and

selecting one of the identified one or more API methods.

9. A method as recited in claim 7, wherein the portion of the test includes one or more of a Run Process operation, an Action operation, a Verify operation, a Set Property operation, a Sleep operation, a Wait For State operation, and a Registry operation.

10. A method as recited in claim 7, wherein calling at least one of the one or more API methods comprises calling each of the at least one API methods using one or more attributes of an operation in the portion of the test.

11. A computer readable media having stored thereon a data structure comprising:

a first data field containing data representing a step in a test of a user interface of a program;

a second data field containing data representing a user interface control of the user interface;

a third data field containing data representing an action to be taken, as part of the step in the test, on the user interface control; and

a fourth data field functioning to delimit the end of the data structure.

12. A computer readable media as recited in claim 11, wherein the data structure is in an eXtensible Markup Language (XML) format.

13. A computer readable media as recited in claim 11, wherein the action to be taken is identified by an Action operation having a plurality of attributes.

14. A computer readable media as recited in claim 13, wherein the plurality of attributes comprises:

a type attribute that maps to a name of a method in a class in an application program interface (API) library;

a description attribute that describes the action to be taken; and

a data attribute that describes the data to be input to the user interface control as part of the action.

15. A computer readable media as recited in claim 11, wherein the action to be taken comprises a Verify operation that specifies a verification to be performed, the Verify operation having a plurality of attributes.

16. A computer readable media as recited in claim 15, wherein the plurality of attributes comprises one or more of:

an exists attribute that describes a particular item that is to exist;

a state value pair attribute that describes a particular property and a corresponding value the property should have; and

a performance time limit attribute that specifies a particular amount of time within which a particular item should exist.

17. A computer readable media as recited in claim 11, wherein the action to be taken comprises a Set Property operation that changes the value of a property of the user interface control.

18. A computer readable media as recited in claim 11, wherein the action to be taken comprises a Run Process operation that runs an executable.

19. A computer readable media as recited in claim 11, wherein the action to be taken comprises a Wait For State operation that causes a test engine to pause the test until a state specified in the Wait For State operation occurs.

20. A computer readable media as recited in claim 11, wherein the action to be taken comprises a Registry operation that allows an operating system registry to be acted on.