Method and system for testing graphical user interface programs

• US 5,634,002 A
• Filed: 05/31/1995
• Issued: 05/27/1997
• Est. Priority Date: 05/31/1995
• Status: Expired due to Fees

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Jervis, Robert, Polk, George A., Kern, John S., Ivanovic, Vladimir G., DeLong, Rance, Muller, Hans E.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Palys, Joseph E.
• Application Number:
  US08/455,583
• Time in Patent Office: 727 Days
• Field of Search: 395/183.14, 395/183.13, 395/183.15, 395/184.01, 395/183.22
• US Class Current: 714/38.14
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable

Abstract

In a preferred embodiment, the present invention provides an improved method and system for testing a graphical user interface program. The preferred embodiment provides improved performance over prior methods because it decouples the testing of an program'"'"'s engine component from the testing of its GUI component. The preferred method begins the testing process by invoking test functions that send data to the program'"'"'s engine component. The data simulates user action on the graphical user interface of the program. In response to receiving the data, the engine component processes the simulated user action as if it had been sent from the graphical user interface component. The preferred method captures the results of this processing and uses the results to determine whether the engine component is performing properly. By testing the engine component without invoking the graphical user interface component, the preferred embodiment reduces the overall time spent testing the GUI program and allows the testing of the program to begin at an earlier point in the development process than had earlier been possible.

Claims

1. A method executable in a computer system for testing a graphical user interface program, the program including a first component and a second component, the computer system including a processor, a memory, and a mechanism for communicating between the processor and the memory, the memory including the program and a test function component, the method comprising the steps of:

initiating execution of a test function from the test function component;

in response to execution of the test function, directly initiating execution of the first component;

capturing data produced by the first component; and

determining whether the captured data indicates that the first component is performing properly,

whereby execution of the first component is not initiated by the second component in response to the execution of the test function.

2. The method of claim 1 wherein the step of initiating execution of the test function further includes the steps of:

selecting from a test script, a request to initiate execution of at least one test function from the test function component;

sending the request to the program; and

in response to receiving the request, initiating execution of the test function identified in the request.

3. The method of claim 2 wherein the test script is implemented as a first process and the graphical user interface program is implemented as a second process.

4. The method of claim 2 wherein a component, distinct from the test script and the program, implements the steps of selecting and sending.

5. The method of claim 1 wherein the test function component is included in the graphical user interface program.

6. The method of claim 5 further including the step of converting the graphical user interface program, including the test function component, into an object file.

7. The method of claim 1 wherein the test function component is part of a library.

8. The method of claim 7 wherein the library is dynamically linked to the graphical user interface program.

9. The method of claim 1 further including the step of testing the second component by examining whether a callback mechanism is invoked in response to receiving data in the program.

10. The method of claim 1 wherein the step of determining is performed by a test script.

11. A method executable in a computer system for testing a graphical user interface program, the program including an engine component and a graphical user interface component, the computer system including a display device, a processor, and a memory, the memory including the program and a test function component, the method comprising the steps of:

selecting from a test script, a request to initiate execution of at least one test function from the test function component;

sending the request to the program;

in response to receiving the request, initiating execution of the test function identified in the request;

in response to execution of the test function, initiating execution of the graphical user interface component;

capturing data produced by the graphical user interface component; and

determining whether the captured data indicates that the graphical user interface component is performing properly,

whereby the graphical user interface component is tested without initiating execution of the engine component.

12. A method executable in a computer system for testing a graphical user interface program, the program including a first component and a second component, the computer system including a processor, a memory, and a mechanism for communicating between the processor and the memory, the memory including the program and a test function component, the method comprising the steps of:

providing a first mechanism for initiating execution of a test function from the test function component;

providing a second mechanism, responsive to execution of the test function, for directly initiating execution of the first component;

providing a third mechanism for capturing data produced by the first component; and

providing a fourth mechanism for determining whether the captured data indicates that the first component is performing properly,

whereby execution of the first component is not initiated by the second component in response to the execution of the test function.

13. The method of claim 12 wherein the step of providing a mechanism for initiating execution of the test function further includes the steps of:

providing a fifth mechanism for selecting from a test script, a request to initiate execution of at least one test function from the test function component;

providing a sixth mechanism for sending the request to the program; and

providing a seventh mechanism, responsive to receiving the request, for initiating execution of the test function identified in the request.

14. A method executable in a computer system for testing a graphical user interface program, the program including an engine component and a graphical user interface component, the computer system including a display device, a processor, and a memory, the memory including the program and a test function component, the method comprising the steps of:

providing a first mechanism for selecting from a test script, a request to initiate execution of at least one test function from the test function component;

providing a second mechanism for sending the request to the program;

providing a third mechanism, responsive to receiving the request, for initiating execution of the test function identified in the request;

providing a fourth mechanism, responsive to execution of the test function, for initiating execution of the graphical user interface component;

providing a fifth mechanism for capturing data produced by the graphical user interface component; and

providing a sixth mechanism for determining whether the captured data indicates that the graphical user interface component is performing properly,

whereby the graphical user interface component is tested without initiating execution of the engine component.

15. A computer system for testing a graphical user interface program, the program including a first component and a second component, the computer system including a processor, a memory, and a mechanism for communicating between the processor and the memory, the memory including the program and a test function component, the computer system comprising:

a first program mechanism configured to initiate execution of a test function from the test function component;

a second program mechanism, responsive to execution of the test function and configured to directly initiate execution of the first component;

a third program mechanism configured to capture data produced by the first component; and

a fourth program mechanism configured to determine whether the captured data indicates that the first component is performing properly,

whereby execution of the first component is not initiated by the second component in response to execution of the test function.

16. A computer system for testing a graphical user interface program, the program including an engine component and a graphical user interface component, the computer system including a display device, a processor, and a memory, the memory including the program and a test function component, the computer system comprising:

a first program mechanism configured to select from a test script, a request to initiate execution of at least one test function from the test function component;

a second program mechanism configured to send the request to the program;

a third program mechanism responsive to receiving the request and configured to initiate execution of the test function identified in the request;

a fourth program mechanism responsive to execution of the test function and configured to initiate execution of the graphical user interface component;

a fifth program mechanism configured to capture data produced by the graphical user interface component; and

a sixth program mechanism configured to determine whether the captured data indicates that the graphical user interface component is performing properly,

whereby the graphical user interface component is tested without initiating execution of the engine component.

17. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for testing a graphical user interface program, the program storage device including an engine component, a graphical user interface component, and a test function component, the method comprising the steps of:

initiating execution of a test function from the test function component;

in response to execution of the test function, directly initiating execution of the engine component;

capturing data produced by the engine component; and

determining whether the captured data indicates that the engine component is performing properly,

whereby execution of the engine component is not initiated by the graphical user interface component.

18. The method of claim 17 wherein the step of initiating execution of the test function further includes the steps of:

selecting from a test script, a request to initiate execution of at least one test function from the test function component;

sending the request to the program; and

in response to receiving the request, initiating execution of the test function identified in the request.

19. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for testing a graphical user interface program, the program storage device including an engine component, a graphical user interface component, and a test function component, the method comprising the steps of:

selecting from a test script, a request to initiate execution of at least one test function from the test function component;

sending the request to the program;

in response to receiving the request, initiating execution of the test function identified in the request;

in response to execution of the test function, initiating execution of the graphical user interface component;

capturing data produced by the graphical user interface component; and

determining whether the captured data indicates that the graphical user interface component is performing properly,

whereby the graphical user interface component is tested without initiating execution of the engine component.