Automated test case verification that is loosely coupled with respect to automated test case execution

• US 20060075303A1
• Filed: 09/29/2004
• Published: 04/06/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,823,132 B2
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/3672 Test management

Abstract

A system and method for verifying the systemic results of an action applied to an application and for providing the expected state of the application at any time or on demand, in which a verification manager determines an expected application state and a current application state of the application, a test case in communication with the verification manager executes the action, and the verification manager compares the expected application state and the current application state.

Claims

1. A system for verifying a plurality of results of an action applied to an application, comprising:

an expected state generator for calculating an expected result of applying the action to the application and for updating an expected application state; and

a verification manager for maintaining a current application state and comparing the expected application state with the current application state.

2. The system of claim 1, wherein the expected state generator determines the expected application state prior to execution of the action.

3. The system of claim 1, wherein the expected state generator determines the expected application state on demand.

4. The system of claim 1, further comprising an expected state generator for communicating to the verification manager an expected component state.

5. The system of claim 4, wherein the expected state generator is external to the verification manager.

6. The system of claim 4, further comprising a component database in communication with the expected state generator, wherein the component database facilitates the expected state generator in determining the expected component state of the component.

7. The system of claim 1, further comprising a test case in communication with and independent of the verification manager for executing the action.

8. The system of claim 1, wherein the action comprises:

a stimulus; and

a parameter.

9. The system of claim 1, wherein the action is at least one of a functional test and an integration test.

10. The system of claim 1, further comprising an expected application state data structure and a current application state data structure.

11. The system of claim 10, wherein the expected application state data structure comprises information received from an expected state generator.

12. The system of claim 10, wherein the current application state data structure comprises information received from the verification manager.

13. The system of claim 1, wherein the verification manager compares the expected application state with the current application state offline.

14. The system of claim 1, wherein the verification manager compares the expected application state with the current application state online.

15. The system of claim 1, wherein the expected state generator is loaded from at least one of a database and a network location.

16. The system of claim 1, wherein the verification manager provides a notification of the comparison of the expected application state with the current application state.

17. The system of claim 16, wherein the notification is completed offline.

18. A computer-readable medium having stored thereon a data structure, comprising:

a first data field stored in a verification manager containing data representing an expected application state of an application based on an action to be implemented on the application; and

a second data field stored in the verification manager containing data representing a current application state of the application after applying the action,

wherein the action is defined and applied by a test case that is independent of the verification manager.

19. The computer-readable medium of claim 18, wherein a plurality of component devices provide data to the first and second data fields with regard to respective components of the application.

20. A method for verifying results of an action applied to an application, comprising:

saving a current application state of the application;

calculating an expected application state from an action to be applied to the application;

saving the expected application state;

executing the action;

updating the current application state of the application; and

comparing the expected application state of the application and the current application state of the application.

21. The method of claim 20, further comprising creating a copy of an initial current state.

22. The method of claim 20, further comprising receiving an expected component state expected as a result of applying the action to a component of the application.

23. The method of claim 22, wherein the expected component state is stored in an expected application state data structure.

24. The method of claim 22, wherein the expected component state is determined by an expected state generator.

25. The method of claim 24, wherein the expected state generator is located external to the verification manager.

26. The method of claim 20, further comprising:

notifying the test case if the expected and current application states are not substantially equal.

27. The method of claim 20, wherein the comparing step is completed using XML.

28. The method of claim 20, wherein the step of saving a current application state of the application is completed after the action is applied.

29. The method of claim 20, wherein the step of saving the expected application state is completed before the action is completed.

30. A computer-readable medium having computer-executable instructions for performing steps comprising:

calculating an expected application state from an action to be applied to the application;

executing the action;

determining a current application state of the application; and

comparing the expected application state of the application and the current application state of the application.

31. The computer-readable medium of claim 30, having further computer-executable instructions for performing the step of receiving an expected component state expected as a result of applying the action to a component of the application.

32. The computer-readable medium of claim 31, having further computer-executable instructions for performing the step of storing the expected component state in an expected application state data structure.

33. The computer-readable medium of claim 31, having further computer-executable instructions for performing the step of providing notification if the expected application state is not substantially equal to the current application state.