How the Test Recorder Works

Page restrictions apply
Added by Barbara Weinstein, last edited by Jesse Costello-Good on Aug 11, 2009

The Test Recorder listens for GI level events, called model events, and records any that have the potential to change the state of the application. When a recording is played back, the application state is updated as if a user were interacting directly with the application.

There are two types of events that may change the state of the application:

An event with a registered event handler. Because the event handler typically calls application logic, it can cause the state of the application to change. Event handlers are set in the Events Editor palette in General Interface Builder.

Specific events known by the system to change the state of the application. These include jsxshow on Tab, jsxselect on Select, and others that cause the display or value of a GUI control to change. These are recorded because they change the state of the application, even if nothing is listening for them. By contrast, an execute event, such as a mouseover, does not change the state of the application and is not recorded, unless custom logic is added.

For information on how to design custom GUI controls that are compatible with the Test Recorder see Designing Recordable Controls.

By restricting the recorded events to those that are important to the functional behavior of the application, the Test Reorder helps you construct useful test cases with a minimum of extraneous noise.

About the General Interface Test Recorder

Chapter 22 Using the Test Recorder

Launching the Test Recorder

Expand all Collapse all

How the Test Recorder Works

Contents

Labels