System and methods for improved program testing

• US 5,475,843 A
• Filed: 10/21/1993
• Issued: 12/12/1995
• Est. Priority Date: 11/02/1992
• Status: Expired due to Term

• Current Assignee: Borland Software Corporation (Open Text Corporation)
• Original Assignee: Borland International, Inc. (Open Text Corporation)
• Inventors: Halviatti, Ramin L., Potts, Richard J.
• Primary Examiner(s): Heckler, Thomas M.
• Application Number:
  US08/140,904
• Time in Patent Office: 782 Days
• Field of Search: 395/155, 395/161, 395/700, 395/650
• US Class Current: 717/124
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06F 9/4812 by interrupt, e.g. masked
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G09B 19/0053 Computers, e.g. programming

Abstract

The present invention includes a Computer-based Training system (CBT) having one or more Application Translation Units (ATUs), a Message Engine, and a Script Engine. For one or more target applications of interest, an ATU is provided for processing events specific to that application, thereby trapping events and translating them into abstract messages or "meta-messages" for conveying information about a particular event to the system. A computer-aided software testing embodiment of the present invention is also described. The system provides prefabricated building blocks for constructing a high-level model of an application'"'"'s User Interface (UI). This high-level model serves as a middle ground between test scripts and the application being tested. The knowledge of how a given UI element is controlled or how it can be observed is retained in the model rather than in a test script. Consequently, the test script consists of easy-to-maintain, high-level testing commands only.

Claims

1. A computer-aided system for testing operation of an application program having a user interface, the system comprising:

means for storing a library of generic element models, each said generic element model encapsulating functionality and behavior for a single user interface element;

means for creating a test model of said application program by combining selected ones of said generic user interface elements into at least one application-specific testing model, each said at least one application-specific testing model representing a high-level model for a specific user interface component for the application program;

message engine means for monitoring events during operation of the application program; and

script engine means for specifying actions of said test model to be undertaken upon occurrence of selected ones of the events.

2. The system of claim 1, wherein user interface elements modeled by said generic element models include selected ones of a push button, a check box, a list box, and a text object.

3. The system of claim 1, wherein specific user interface components for the application program include selected ones of a menu, a toolbar, a dialog, a client-area window, and a status line.

4. The system of claim 1, wherein said events include system events generated by operating system software.

5. The system of claim 1, wherein said events include application-specific events which result from non-system events occurring within said application program.

6. The system of claim 1, wherein functionality for a user interface element includes how the element responds to occurrence of events during operation of the application program.

7. The system of claim 1, wherein behavior for a user interface element includes screen attributes specifying how the element is displayed on a screen during operation of the application program.

8. The system of claim 7, wherein said screen attributes include selected ones of screen position, size, color, and font.

9. The system of claim 7, wherein said screen attributes include a default state.

10. The system of claim 7, further comprising:

a database for storing expected values of screen attributes for user interface elements of the application program.

11. The system of claim 10, further comprising:

comparison means for comparing expected values stored in the database to actual values for user interface elements of the application program at runtime.

12. The system of claim 11, further comprising:

self-testing means for automatically invoking default functionality of each said at least one application-specific testing model for the application program and comparing actual behavior of each said at least one application-specific testing model with its expected behavior.

13. The system of claim 1, wherein said script engine means operates in response to a test script, said test script including high-level commands specifying a test in terms of actions to occur at selected ones of specific user interface components for the application program.

14. The system of claim 1, wherein said means for creating a test model includes:

means for decomposing the application program into irreducible user interface components.

15. The system of claim 14, wherein said means for decomposing includes:

means for reading resource information from the application program, said resource information specifying creation of user interface elements of the application program at runtime.

16. The system of claim 14, wherein said means for decomposing includes:

means for operating the application program and monitoring creation of user interface elements of the application program at runtime.

17. The system of claim 1, further comprising:

means for dynamically binding each said at least one application-specific testing model with the actual specific user interface component it represents.

18. The system of claim 1, wherein said specified actions include user events for simulating operation of the application program by a user.

19. The system of claim 18, wherein said user events include selected ones of keyboard device and mouse device input events.

20. In a computer system, a method for testing operation of an application program having a user interface, the method comprising:

(a) creating a test model of said application program by combining pre-supplied generic element models into at least one application-specific testing model, each said generic element model encapsulating functionality and behavior for a single user interface element, each said at least one application-specific testing model representing a high-level model for a specific user interface component for the application program;

(b) monitoring events during operation of the application program; and

(c) specifying actions of said test model to be undertaken upon occurrence of selected ones of the events, whereupon a specified action in the application program is effected in response to occurrence of said selected events.

21. The method of claim 20, wherein said generic element models represent selected ones of a push button, a check box, a list box, and a text object.

22. The method of claim 20, wherein specific user interface components for the application program include selected ones of a menu, a toolbar, a dialog, a client-area window, and a status line.

23. The method of claim 20, wherein said events include selected ones of events generated by operating system software and events occurring within said application program.

24. The method of claim 20, wherein behavior for a user interface element includes screen attributes specifying how the element is displayed on a screen during operation of the application program.

25. The method of claim 24, wherein said screen attributes include selected ones of screen position, size, color, and font.

26. The method of claim 24, further comprising:

storing in a database expected values of screen attributes for user interface elements of the application program.

27. The method of claim 26, further comprising:

comparing expected values stored in the database to actual values for user interface elements of the application program at runtime.

28. The method of claim 27, further comprising:

sequentially testing each specific user interface component which is modeled by invoking default functionality of each said at least one application-specific testing model for the application program and comparing actual behavior of each said at least one application-specific testing model with its expected behavior.

29. In a computer system, a method for testing operation of a graphical user interface, the method comprising:

(a) creating for the graphical user interface at least one model for testing user interface elements, each said at least one model being constructed from a set of generic objects representing basic user interface elements;

(b) providing each model a link to its actual user interface element;

(c) storing for each model a set of expected characteristics that its actual user interface element is to exhibit;

(d) trapping a request to create a user interface element; and

(e) in response to a trapped request, loading a model for the user interface element which is requested to be created and comparing its actual characteristics to said stored expected ones.

30. The method of claim 29, further comprising:

(f) providing each model with a set of methods for simulating operation of its user interface element; and

(g) simulating runtime operation of the graphical user interface by invoking methods for selected ones of the user interface elements.

33. The method of claim 29, wherein specific user interface elements include selected ones of a menu, a toolbar, a dialog, a client-area window, and a status line.

34. The method of claim 29, wherein step (d) includes:

registering an interest in a system message which indicates that a user interface element is about to be created; and

monitoring for occurrence of said system message.

35. The method of claim 34, wherein said graphical user interface includes Microsoft®

Windows graphical user interface, and said system message is a Microsoft®

Windows CreateWindow message.

31. The method of 30, wherein step (g) includes:

providing a test script, said test script having high-level commands for simulating operation of the graphical user interface.

32. The method of 31, wherein said high-level commands include a general format of:

space="preserve" listing-type="equation">[object].[action]

where [object] specifies a user interface element and [action] specifies a simulated operation for the object.