Test automation stack layering

• US 7,398,514 B2
• Filed: 09/29/2004
• Issued: 07/08/2008
• Est. Priority Date: 09/29/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hunter, Michael J., Gallacher, Michael D., Ulrich, Adam M.
• Primary Examiner(s): Zhen; Wei Y.
• Assistant Examiner(s): Deng; Anna
• Application Number:
  US10/953,402
• Publication Number:
  US 20060070035A1
• Time in Patent Office: 1,378 Days
• Field of Search: 717124-126, 717/131, 717162-163
• 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 for testing a software application, the system comprising a processor and configured to:

receive 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 being associated with a user action of the software application, the user action comprising a general action a user may take with regard to the software application and without regard to any specific set of execution details employed to implement the user action, each user action being implemented by any of a plurality of sets of specific execution details, each set of specific execution details setting out a corresponding execution path of user commands;

select a behavior associated with the user action, the behavior also being associated with a specific execution path for the user action; and

execute the test case using the selected specific execution path, the selected specific execution path referencing an object in a physical layer of the multi-layered library, the object in the physical layer corresponding to the object in the logical layer and comprising a set of specific execution details relating to the user action of the corresponding object in the logical layer and to the selected specific execution path.

2. The system of claim 1, further configured to send a notification that the test case will be executed.

3. The system of claim 1, further configured to save a pre-test expected state resulting from execution of the test case.

4. The system of claim 3, further configured to compare 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.

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

6. The system of claim 1, wherein the test case resides in a test case layer of a 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 a 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 objects associated with verification of test results are separated from objects associated with execution options.

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 a logical layer of a test 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 objects associated with verification of test results are separated from objects associated with execution options.

14. The system of claim 1, wherein an object associated with verification of test results is stored in a logical layer of a test 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 testing a software application and 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 being associated with a user action of the software application, the user action comprising a general action a user may take with regard to the software application and without regard to any specific set of execution details employed to implement the user action, each user action being implemented by any of a plurality of sets of specific execution details, each set of specific execution details setting out a corresponding execution path of user commands;

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

executing the test case using the selected specific execution path, the selected specific execution path referencing an object in a physical layer of the multi-layered library, the object in the physical layer corresponding to the object in the logical layer and comprising a set of specific execution details relating to the user action of the corresponding object in the logical layer and to the selected specific execution path.

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 storage medium having stored thereon computer executable instructions for implementing a method for creating efficiencies in test case creation and maintenance for testing a software application and 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 being associated with a user action of the software application, the user action comprising a general action a user may take with regard to the software application and without regard to any specific set of execution details employed to implement the user action, each user action being implemented by any of a plurality of sets of specific execution details, each set of specific execution details setting out a corresponding execution path of user commands;

sending a notification that the test case will be executed;

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

executing the test case using the selected specific execution path, the selected specific execution path referencing an object in a physical layer of the multi-layered library, the object in the physical layer corresponding to the object in the logical layer and comprising a set of specific execution details relating to the user action of the corresponding object in the logical layer and to the selected specific execution path; and

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

22. The computer-readable storage 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 storage 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 storage medium of claim 21, comprising further instructions for:

parsing the test case.

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

sending a notification that the test case has been executed.