Package junit.extensions.awt.editor

Provides support for editing AWT test scripts.

See:
          Description

Class Summary
AWTEventRecorder Provides recording of raw AWT events.
ButtonClickRecorder That means mouse button click, not GUI button click.
ComponentBrowser Browse an existing component hierarchy.
ComponentNode  
ComponentPropertyModel  
EventRecorder Provides recording of raw AWT events, attempting to parse them as high-level semantic events.
KeyStrokeRecorder Record a key stroke (press and release).
MenuSelectionRecorder Record a normal menu selection.
PopupMenuSelectionRecorder Record a normal menu selection.
Recorder Template for recording AWTEvents and converting them into a more semantic event.
ReferencesModel Formats a Script for display in a table.
ScriptEditor Costello, the editor for Abbot scripts.
ScriptModel Formats a Script for display in a table.
ScriptTable Provides a component to edit a test script.
TestSelector A test class selector.
TestSelector.TestCellRenderer Renders TestFailures in a JList
TextRecorder  
XMLEditor An editor for an XMLifiable object.
 

Exception Summary
RecordingCanceledException  
 

Package junit.extensions.awt.editor Description

Provides support for editing AWT test scripts.

Recorders

Recorders capture a raw event stream and turn it into a ComponentTester action method. This class is designed to recognize and capture a distinct semantic event from basic OS events as they are generated by the user. For example, the ButtonClickRecorder waits for button press, release, and click events in any component in the tested GUI, saving them as a "Click" action (which is provided by the base ComponentTester class).

The ESC key will cancel any recording currently in progress (with the exception of the EventRecorder, which uses ESC to indicate the end of an event stream, and KeyStrokeRecorder, which might actually want to capture the ESC keystroke).

The EventRecorder class tries to convert an event stream into any of the individual semantic events recorded by the other Recorder classes. The main benefit of the individual Recorder classes is that they will ignore all events that do not contribute to what they are recording, while the EventRecorder will record those possibly extraneous events. When starting a new script, it's generally easier to use the EventRecorder at first, and then use the individual Recorders for fine tuning the test.

Recorders are only used within the script editor.