Automated GUI interface testing

• US 5,781,720 A
• Filed: 08/21/1996
• Issued: 07/14/1998
• Est. Priority Date: 11/19/1992
• Status: Expired due to Fees

• Current Assignee: Borland Software Corporation (Open Text Corporation)
• Original Assignee: Segue Software, Inc. (Open Text Corporation)
• Inventors: Laroche, David Christopher, Parker, Marsten Hugh, Kepple, Laurence Ralph, Sklar, Leah Ruth
• Primary Examiner(s): Sheikh, Ayaz R.
• Assistant Examiner(s): PANCHOLI, JIGAR K
• Application Number:
  US08/697,262
• Time in Patent Office: 692 Days
• Field of Search: 395/575, 395/155, 395/156-161, 395/183.14, 395/573
• US Class Current: 714/38.11
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3457 Performance evaluation by simulation
• 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
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06K 13/0825 the ejection arrangement being of the push-push kind

Abstract

A method for automated testing of both new and revised computer application programs which use a Graphical User Interface (GUI). Simulated user events such as keyboard or mouse actions are automatically input into the GUI interface. The GUI is then monitored to observes the changes to the GUI in response to the input. The invention comprises a test script which is written in a high level programming language, a test executive which executes the test script, and a test driver which provides the interface to the GUI. The test script is directed towards operation on logical objects, instead of GUI-specific references. The primary responsibility of the test executive is to convert GUI-independent references into GUI-specific references. The test driver takes the GUI-specific references from the test executive and performs the actual interface to the GUI objects. A uniform hierarchial naming scheme is employed to identify each Logical Screen Element (LSE) under test, LSEs being the objects used in the GUI environment to interface with the user.

Claims

1. A method of testing an application program'"'"'s use of a first Graphical User Interface (GUI), said application program and a test script executing concurrently, said test script containing a sequence of test instructions, said method comprising:

simulating a user action directly to said first GUI in response to said test instructions;

monitoring said GUI for actual alterations in one or more logical screen elements, said logical screen elements originating from said execution of said application program;

comparing said actual alterations to expected alterations; and

reporting an error if said actual alterations are not equal to said expected alteration.

2. A method according to claim 1 further comprising naming said logical screen elements in said test script according to a non-GUI specific protocol.

3. A method according to claim 2 wherein a test program executes said test script, said test program performing said translating step.

4. A method according to claim 3 wherein said simulating step further comprises:

said test program executing one or more of said test instructions from said test script, said one or more test instructions representing said user action;

generating one or more GUI specific in response in response to said execution of said one or more test instructions; and

transmitting said one or more GUI specific instructions to said GUI.

5. A method according to claim 3 wherein said simulating step further comprises:

waiting a predetermined amount of time for said actual changes; and

raising an exception if said actual changes do not occur within said predetermined amount of time.

6. A method according to claim 3 wherein said monitoring step further comprises:

said test program executing a status request from said test script;

generating one or more GUI specific instructions in response to said execution of said status request;

transmitting said one or more GUI specific instructions to said GUI; and

receiving and returning said requested status to said test program.

7. A method of testing an application program'"'"'s use of a first Graphical User Interface (GUI) in a computer system comprising the steps of:

executing the application program;

executing a test script concurrently with the execution of the application program, said test script containing a sequence of non-GUI specific test instructions, the test script execution step comprising the step of simulating a user action directly to said first GUI in response to said test instructions, wherein the test script execution step further comprises translating said test instructions into GUI specific instructions;

monitoring said GUI for actual alterations in at least one display independent logical screen element originating from said execution of said application program, said display independent logical screen element being an object created by said application program within said GUI;

comparing said actual alterations to expected alterations; and

reporting an error if said actual alterations are not equal to said expected alteration.

8. A method of testing an application program'"'"'s use of a first Graphical User Interface (GUI) in a computer system comprising the steps of:

executing the application program;

executing a test script concurrently with the execution of the application program, said test script containing a sequence of non-GUI specific test instructions, the test script execution step comprising the step of simulating a user action directly to said first GUI in response to said test instructions;

monitoring said GUI for actual alterations in at least one display independent logical screen element originating from said execution of said application program, said display independent logical screen element being an object created by said application program within said GUI;

comparing said actual alterations to expected alterations;

reporting an error if said actual alterations are not equal to said expected alteration; and

performing said simulating, monitoring, comparing and reporting steps with respect to a second GUI.

9. A method according to claim 8 wherein said performance with respect to said second GUI is concurrent with testing against said first GUI.

10. A method according to claim 9 wherein said second GUI is different from said first GUI.

11. A method according to claim 9 wherein said second GUI resides on a different computer system from said first GUI.

12. A method of testing an application program'"'"'s use of a first Graphical User Interface (GUI) in a computer system comprising the steps of:

executing the application program;

executing a test script containing a sequence of non-GUI specific test instructions concurrently with the execution of the application program, comprising the steps of

reading one of said test instructions from said test script,

searching for a display independent logical screen element, said display independent logical screen element being an object created by said application within said GUI, said one of said test instructions requesting an action against said display independent logical screen element; and

upon finding said display independent logical screen element, performing said requested action;

monitoring said display independent logical screen element for actual alterations;

comparing said actual alterations to expected alterations; and

raising an exception if said actual alterations are not equal to said expected alteration.

13. A method according to claim 12 further comprising performing non-GUI related actions if said one of said test instructions does not involve said GUI.

14. A method according to claim 12 further comprising translating said test instruction from said test script.

15. A method according to claim 12 further comprising:

waiting a predetermined amount of time during said search for said logical screen element; and

raising an exception if said first predetermined amount of time expires prior to finding said logical screen element.

16. A method according to claim 12 further comprising:

testing said logical screen element after it is found, said test determining if said logical screen element is in a desired state for said requested action.

17. A method according to claim 16 further comprising:

repeating said test of said logical screen element for a predetermined amount; and

raising an exception if said predetermined amount of time expires prior to said logical screen element attaining said desired state.

18. A method according to claim 12 wherein said requested action simulates a user input, said method further comprising:

waiting a predetermined amount of time during said monitoring of said logical screen element; and

raising an exception if said predetermined amount of time expires and no alterations occur in said logical screen element.

19. A system for testing an application program'"'"'s use of a Graphical User Interface (GUI), said testing system comprising:

a least one computer system, said GUI and said application residing on said computer system;

a test script containing a sequence of non-GUI specific test instructions;

a test program, said test program having means for translating said non-GUI specific test instructions into GUI specific test instructions; and

a test driver, said test driver having means for generating screen dependent instructions from said GUI specific test instructions.

20. A system according to claim 19 further comprising:

an interface between said application and said GUI; and

a first monitoring means in said test driver for monitoring said interface between said application and said GUI.

21. A system according to claim 20 further comprising a second monitoring means in said test driver for monitoring changes in said GUI.

22. A system according to claim 19 further comprising:

a physical screen element manager, PSEM in said GUI, said PSEM having an interface for user devices; and

an interface between said test driver and said PSEM.

23. A system according to claim 22 further comprising said generation means in said test driver using said interface between said test driver and said PSEM.

24. A method of testing an application program'"'"'s use of a first Graphical User Interface (GUI), said first GUI containing logical screen elements (LSE) generated by said application, said method comprising:

requesting an action against a named LSE, said LSE being named in a non-GUI specific manner;

resolving said non-GUI specific name of said LSE into a GUI specific reference;

generating one or more GUI specific commands which accomplish said requested action; and

communicating said one or more GUI specific commands to said GUI.

25. A method according to claim 24 wherein said resolving step comprises constructing a window tag for said named LSE, said window tag uniquely identifying said LSE in GUI specific terms.

26. A method according to claim 25 wherein said constructing step comprises:

identifying a class of said named LSE, said class being one of a set of classes defining characteristics of all LSEs in said GUI;

extracting a default window tag from said class definition;

determining a tag part from a previous declaration of said named LSE; and

combining said default window tag and said tag part into said window tag.

27. A method according to claim 26 wherein said named LSE contains several levels of names, said resolution step further comprises repeating said identifying, extracting, determining and combining step for each of said levels in said name.

28. A method according to claim 24 wherein said generating step comprises:

calling an internal function which corresponds to said requested action, said GUI specific reference to said LSE being passed to said internal function as a parameter; and

developing said one or more GUI specific commands using said GUI specific reference to said LSE.

29. A method according to claim 24 further comprising:

testing said GUI for expected alterations in said named LSE;

reporting an error if said expected alteration do not occur.

30. A method according to claim 29 wherein said testing step comprises:

monitoring said GUI for actual alterations in said LSE; and

comparing said actual alterations to said expected alterations.

31. A method according to claim 30 further comprising retrieving said expected alterations from a test database.

32. A method according to claim 30 further comprising storing said reported error in an error database.