Test automation stack layering

• US 20060070035A1
• Filed: 09/29/2004
• Published: 03/30/2006
• Est. Priority Date: 09/29/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hunter, Michael J., Gallacher, Michael D., Ulrich, Adam M.
• Granted Patent: US 7,398,514 B2
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

Separation of aspects of automated testing into architectural layers enables automated testing to occur sooner and faster and to provide more comprehensive testing. A physical layer provides an object model over the user interface of an application. A logical layer provides an object model around the functions of an application. A test case executor may execute a test case. A data manager may ensure variability in test data. A behavior manager may determine execution details appropriate for a particular test case. A verification manager may perform the verification processing after the test case has executed.

Claims

1. An automated test system comprising:

an architectural test automation stack comprising;

a set of objects comprising a logical layer, the set of objects of the logical layer associated with a set of user actions of an application to be tested, the set of objects of the logical layer having direct access to a set of objects of a physical layer; and

the set of objects of the physical layer, the set of objects of the physical layer comprising a set of objects directed to execution options associated with the set of user actions.

2. The system of claim 1, further comprising a test case, the test case referencing an object in the set of objects of the logical layer.

3. The system of claim 1, further comprising a test case, the test case not referencing an object in the set of objects of the physical layer.

4. The system of claim 2, wherein the test case comprises no verification code.

5. The system of claim 2, wherein the test case comprises no execution options.

6. The system of claim 2, wherein the test case resides in a test case layer of the test automation stack.

7. The system of claim 1, further comprising a data manager, the data manager providing variable test data required by a test case.

8. The system of claim 1, wherein objects associated with test data selection are stored in a second logical layer not in the test automation stack.

9. The system of claim 1, further comprising a behavior manager, the behavior manager selecting execution options for a test case.

10. The system of claim 1, wherein an object associated with an execution path for a user action of the set of user actions of the application to be tested is stored in an execution behavior logical layer not in the automation stack.

11. The system of claim 1, wherein an object associated with an execution path for a user action of the set of user actions of the application to be tested is stored in the logical layer of the automation stack.

12. The system of claim 1, further comprising a verification manager, the verification manager determining results of execution of a test case.

13. The system of claim 1, wherein an object associated with verification of test results is stored in a verification layer not in the automation stack.

14. The system of claim 1, wherein an object associated with verification of test results is stored in the logical layer of the automation stack.

15. The system of claim 12, wherein the verification manager compares actual results of execution of the test case with expected results of execution of the test case.

16. A method for creating efficiencies in test case creation and maintenance comprising:

receiving a test case, the test case comprising at least one statement, the at least one statement referencing an object in a logical layer of a multi-layered library, the object associated with a user action;

selecting a behavior associated with the user action, the behavior associated with a specific execution path for the user action;

executing the test case using the selected specific execution path, the specific execution path referencing an object in a physical layer of the multi-layered library.

17. The method of claim 16, further comprising:

sending a notification that the test case will be executed.

18. The method of claim 16, further comprising:

saving a pre-test expected state resulting from execution of the test case.

19. The method of claim 18, further comprising:

comparing the pre-test expected state resulting from execution of the test case with an actual post-test state resulting from execution of the test case.

20. The method of claim 16, wherein objects associated with verification of test results are separated from objects associated with execution options.

21. A computer-readable medium comprising computer executable instructions for:

receiving a test case, the test case comprising at least one statement, the at least one statement referencing an object in a logical layer of a multi-layered library, the object associated with a user action;

sending a notification that the test case will be executed;

selecting a behavior associated with the user action, the behavior associated with a specific execution path for the user action; and

executing the test case using the selected specific execution path, the specific execution path referencing an object in a physical layer of the multi-layered library; and

comparing a pre-test expected state with a post-test actual state.

22. The computer-readable medium of claim 21, comprising further instructions for:

saving a pre-test expected state resulting from execution of the test case.

23. The computer-readable medium of claim 22, comprising further instructions for:

comparing the pre-test expected state resulting from execution of the test case with an actual post-test state resulting from execution of the test case.

24. The computer-readable medium of claim 21, comprising further instructions for:

parsing the test case.

25. The computer-readable medium of claim 21, comprising further instructions for:

sending a notification that the test case has been executed.