Methods and systems for navigating deterministically through a graphical user interface

• US 7,290,245 B2
• Filed: 10/18/2001
• Issued: 10/30/2007
• Est. Priority Date: 10/18/2001
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Skjolsvold, Arild E.
• Primary Examiner(s): Cabeca; John
• Assistant Examiner(s): Bonshock; Dennis G.
• Application Number:
  US09/982,395
• Publication Number:
  US 20030076366A1
• Time in Patent Office: 2,203 Days
• Field of Search: 345/855, 345/854, 345/762, 719/328, 715/855, 715/762, 715/854, 714/37, 714/38, 714/39, 714/29, 717/125, 717/134
• US Class Current: 717/125
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 8/427 Parsing

Abstract

Disclosed is a mechanism for systematically invoking executable features of a software application via its graphical user interface. Also disclosed is a mechanism for generating a map that characterizes operational states of an application as it executes. An application driver selects an action to be performed by the application according to a deterministic mode such as depth-first mode or breadth-first mode. In the depth-first mode of deterministic operation, an action associated with a particular element is explored as deeply as possible, while breadth-first mode explores the application as widely as possible. For each executable feature invoked within the software application, the states encountered during execution are stored within the application map for subsequent retrieval and analysis.

Claims

1. A method for testing at least one software application, the method comprising:

injecting a dynamic link library (DLL) into an executable code of the software application being tested;

installing at least one at least one hook function into an application programming interface (API) of an operating system, the installing performed by the DLL, the at least one hook function configured to monitor for testing operating system messages communicated with the software application during execution of the software application being tested;

retrieving information descriptive of a state of operation of the software application being tested and at least one graphics element rendered during execution of the software application being tested, wherein the information identifies an executable feature associated with the at least one graphics element, and wherein at least some of the retrieved information descriptive of the state of operation is based on messages monitored by way of the at least one hook function;

storing information related to an association between the executable feature and the at least one graphics element and the state of operation of the software application in a map data structure containing information related to at least one graphics element for testing, the association and information being stored in the map data structure during execution of the software application being tested;

automatically selecting an executable feature from the map data structure based on the association stored in the map data structure;

automatically, executing the selected executable feature associated with the graphics element; and

dynamically updating the information related to the state of operation of the software application and the association in the map data structure upon execution of the executable feature.

2. The method of claim 1, further comprising:

dynamically updating information in the map data structure descriptive of at least one second graphics element resulting from the exposure of a new state of operation of the software application in response to the execution of the executable feature;

displaying the at least one second graphics element;

retrieving information descriptive of the state of operation of the software application being tested and the at least one second graphics element rendered during execution of the software being tested, the information including a second executable feature associated with the at least one second graphics element and the new state of operation of the software application;

storing the information descriptive of the new state of operation of the software application being tested and the second executable feature in association with the at least one second graphics element in the map data structure during execution of the software being tested; and

automatically executing the at least one second executable feature stored in association with the second graphics element.

3. The method of claim 1 wherein the retrieving comprises capturing information pertaining to the graphics element and the state of operation of the software application being tested.

4. The method of claim 1, wherein the storing includes updating an indicator associated with the at least one graphics element when the executable feature stored in association with the at least one graphics element is executed.

5. The method of claim 1 wherein the storing includes organizing the retrieved information such that the executable feature stored in association with the at least one graphics element can be interpreted by a computer-executable application capable of accessing the retrieved information.

6. The method of claim 1 wherein the storing includes organizing the retrieved information such that the executable feature stored in association with the at least one graphics element and the state of operation of the software application being tested can be interpreted by a user capable of accessing the retrieved information from memory.

7. The method of claim 1 wherein the automatically selecting comprises automatically selecting an executable feature not previously executed.

8. The method of claim 7 wherein the automatically selecting comprises reviewing an indicator to automatically select an executable feature not previously executed.

9. The method of claim 1 wherein the automatically selecting comprises automatically selecting executable features in a depth-first mode of operation.

10. The method of claim 1 wherein the automatically selecting comprises automatically selecting executable features in a breadth-first mode of operation.

11. The method of claim 1, wherein a state of operation of the software application includes a distinctive set of graphic elements, content, and associated actions of the software application during execution.

12. A system for generating a map, comprising:

a capture agent for retrieving information descriptive of a state of operation of a software application being tested and a plurality of graphics elements rendered during execution of the software application, the information including an executable feature associated with each graphics element, the capture agent including a dynamic link library (DLL) configured to be injected into an executable code of the software application being tested, the DLL further configured to install at least one hook function into an application programming interface (API) of an operating system, wherein the at least one hook function is configured to monitor messages communicated between the operating system and the software application during execution of the software application being tested;

an application driver for storing information in a map data structure related to an association between each executable feature and corresponding graphics element and a state of operation of the software application during execution of the software application being tested, wherein the map data structure contains information related to at least one graphics element for testing;

an application driver for automatically selecting one of the executable features stored in the map data structure based on the information stored in the map data structure;

a command agent for automatically executing the selected executable feature; and

an indicator for tracking a dynamic updating of the information related to the association and the state of operation of the software application in the map data structure upon the automatic execution of the selected executable feature.

13. The system of claim 12 wherein the capture agent is invoked by the application driver.

14. The system of claim 12 wherein the capture agent submits the retrieved information to the application driver.

15. The system of claim 12, wherein the application driver automatically selects one of the executable features that has not been previously executed.

16. The system of claim 12, wherein the application driver reviews the indicator to automatically select the one executable feature.

17. The system of claim 12, wherein the application driver automatically selects executable features according to a depth-first deterministic mode of operation.

18. The system of claim 12 wherein the application driver automatically selects executable features according to a breadth-first deterministic mode of operation.

19. A method for systematically invoking an executable feature of a software application having a graphical user interface, the method comprising:

injecting a dynamic link library (DLL) into an executable code of the software application;

installing at least one hook function into an application programming interface (API) of an operating system, the installing performed by the DLL, the at least one hook function configured to monitor operating system messages communicated with the software application during execution of the software application being tested;

retrieving information descriptive of a state of operation of a software application being tested and at least one graphics element rendered during execution of the software application, the information including an executable feature associated with the at least one graphics element, at least some of the retrieved information descriptive of a state of operation of the software application retrieved by way of messages monitored by the at least one hook function;

storing information related to an association between the executable feature and corresponding graphics element and the state of operation of the software application in a map data structure to contain information related to at least one graphics element for testing, the association and information being stored in the map data structure during execution of the software application;

automatically selecting from the map data structure at least one executable feature associated with a graphics element that has not been previously executed; and

automatically executing the selected at least one executable feature.

20. The method of claim 19 further comprising, in response to executing the selected executable feature:

dynamically updating the information related to the association and the state of operation of the software application in the map data structure upon execution of the selected at least one executable feature;

displaying a second graphics element;

retrieving information descriptive of the second graphics element rendered during execution of the software application and the state of operation of the software application being tested, the information including an association of a second executable feature with the second graphics element and a new state of operation of the software application;

storing the information descriptive of the new state of operation of the software application and the association between the second executable feature and the second graphics element in the map data structure;

automatically selecting from the map data structure an executable feature that has not been previously executed, according to a sequence determined by one of a plurality of deterministic modes of execution of the software application; and

automatically executing the selected executable feature.

21. The method of claim 19, wherein the retrieving comprises capturing information pertaining to the second graphics element.

22. The method of claim 19, wherein the storing comprises updating an indicator associated with the second graphics element when an executable feature stored in association with the graphics element is executed.

23. The method of claim 19, wherein the automatically selecting comprises reviewing an indicator to determine an executable feature not previously executed.

24. The method of claim 19, wherein the automatically selecting includes a depth-first mode of operation.

25. The method of claim 19, wherein the automatically selecting includes a breadth-first mode of operation.