Event handling

Events are unscheduled occurrences or conditions to which you want the target application to respond in a specified manner.
TestPartner supports two categories of events: Waits and Whenevers.


A Wait event tells TestPartner to wait for a specified occurrence before proceeding. Wait events are useful in situations where you
cannot anticipate the amount of time a response will take. An example of a Wait event would be waiting for a system login prompt. When your script is running against a network-based application that requires the user to log in, the amount of time it takes for the login prompt to display may vary. To account for this variance, you can insert a Wait event that instructs your script to wait for the login prompt before
proceeding to type a user name and password.



A Whenever event tells TestPartner to watch for a specific occurrence and, if it occurs, perform a special set of steps. Whenever events are useful for trapping unexpected error conditions during a test run. For example, you can include events in your scripts to recognize when the connection to the server has been interrupted by a communications error or a network system message has been received,
so that the script can report or work around the problem.

In a script, TestPartner automatically inserts the Script_Whenever function by default to handle the whenever event. If a whenever event is inserted into a module, shared module, or class module, you must customize the whenever event handler code. To determine what is performed when a whenever event triggers, TestPartner uses the Script_Whenever function to handle the event

CheckPoints in Test Partner

Check: A check is a definition of what the application should be showing at any particular point.

Bitmap checks — Bitmap checks compare an actual bitmap with a defined bitmap. These checks are used to check the appearance of toolbars, the desktop,
and other windows that contain non-textual information

Clock checks — Clock checks measure the time the system takes to perform a process. Clock checks help you determine how the system performs under
varying CPU or network loads.

Content checks — Content checks test the contents of tables and list controls in a window or web page.This is used for creating checks in listbox.Through this content check we can check how many items are flowing in an list box and what is the default value of the listbox.

Field checks — Field checks enable you to conduct specific types of text comparisons, including date
and time, for individual fields you select in a window or area.

Property checks — Property checks verify the properties of the controls in a dialog or web page or Window.

Text checks — Text checks provide an exact comparison of the text in a window or individual area to defined text.
If you check a whole screen, areas that contain legitimately variable data — such as dates and login IDs — can be ignored.