Automated GUI interface testing

• US 5,600,789 A
• Filed: 11/19/1992
• Issued: 02/04/1997
• Est. Priority Date: 11/19/1992
• Status: Expired due to Term

• Current Assignee: Borland Software Corporation (Open Text Corporation)
• Original Assignee: Segue Software, Inc. (Open Text Corporation)
• Inventors: Sklar, Leah R., Kepple, Laurence R., Parker, Marsten H., Laroche, David C.
• Primary Examiner(s): Harvey, Jack B.
• Assistant Examiner(s): Myers, Paul R.
• Application Number:
  US07/978,936
• Time in Patent Office: 1,538 Days
• Field of Search: 371/19, 364/221.7, 364/267.3, 364/267.4, 364/264.3, 364/266.4, 395/575, 395/155, 395/156-161, 395/183.14
• 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) in a computer system comprising the steps of:

executing the application, the application generating display independent logical screen elements (LSE) within the first GUI in the computer system, said display independent LSEs being objects created by said application program within said GUI;

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

resolving said non-GUI specific name of said display independent LSE into a GUI specific reference, wherein said resolving step comprises constructing a window tag for said named display independent LSE, said window tag uniquely identifying said display independent LSE in GUI specific terms, and wherein said constructing step comprises;

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

extracting a default window tag from said class definition;

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

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

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

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

2. A method according to claim 1 wherein said named display independent 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.