| Home >> All >> abbot >> [ editor Javadoc ] |
| | abbot.editor.actions.* (4) | | abbot.editor.editors.* (14) | | abbot.editor.i18n.* (3) |
| | abbot.editor.recorder.* (32) |
abbot.editor: Javadoc index of package abbot.editor.
Package Samples:
abbot.editor.actions: Provides support for editing Abbot test scripts.
abbot.editor.recorder: Provides support for editing Abbot test scripts.
abbot.editor.editors
abbot.editor.i18n
Classes:
ComponentRecorder: Record basic semantic events you might find on any component. This class handles the following actions: window actions popup menus click (based on coordinates) typed keys basic drag and drop (based on coordinates) InputMethod events (extended character input) Window Actions While these nominally might be handled in a WindowRecorder, they are so common that it's easier to handle here instead. Currently supports tracking show/hide/activate. TODO: move/resize/iconfify/deiconify. Popup Menus Currently only the click/select/click sequence is supported. The press/drag/release version shouldn't be hard ...
Recorder: The Recorder provides a mechanism for recording an event stream and generating one or more script steps from that stream. The base abstract Recorder class handles the logistics of capturing the events, cancellation and termination with proper synchronization. The concrete implementation tracks the individual events to produce the desired high level user action representations. NOTE: when writing a recorder, be very careful not to test for platform-specific behavior, and avoid being susceptible to platform-specific bugs. Please make sure the recorder works on both pointer-focus and click-to-focus ...
SemanticRecorder: Template for recording AWTEvents and converting them into an appropriate semantic event. The EventRecorder class decides which SemanticRecorder to use and handles cancel/termination. Implementations should be named AbstractButtonRecorder, JTableRecorder, etc. The semantic recorders will be dynamically loaded based on the component receiving a given event (compare to ComponentTester). See EventRecorder for implementation details.
EventRecorderTest: Unit test to verify proper capture of multiple user semantic events when parsed from a continuous event stream. FIXME add support to feed the event recorder an event sequence and have it do its cleanup FIXME add support to feed the event recorder an event sequence to record Still want to do the robot generation, 'cuz that'll catch errors on new platforms. Specific event sequences avoid having to throw up an IF.
ScriptEditor: Costello, the editor for Abbot scripts. Acts as a resolver, using the currently in-context script as the component resolver. WARNING: The script editor must never spawn threads or load classes from the event dispatch thread while a script is either running or has been lauched, or risk having its classes loaded by the wrong class loader.
EditorConstants: Common constants for editor actions. NOTE: to add a new editor action, define a constant for it here, add an action for it in abbot.editor.action.EditorActions, create a menu for it in ScriptEditorFrame, and handle it in ScriptEditor. I know that's a lot of entries, I'd like to clean it up.
ComponentRecorderTest: Unit test to verify proper capture of basic user semantic events. A ComponentTester is used to generate the appropriate events, which is significantly easier than reproducing the steps manually. These tests should be run after the ComponentTester tests.
TestSelector: A test class selector. A simple dialog to pick the name of a test suite. Thanks to JUnit for this code. FIXME this currently doesn't scan jar files, only bare classes, and depends on the class path established at application launch.
ReferencesModel: Formats a Script for display in a table. Keeps track of "open" nodes to create a tree-like display NOTE: this is a brute-force implementation with no attempts at optimization. But it's a very simple tree+table implementation.
ScriptModel: Formats a Script for display in a table. Keeps track of "open" nodes to create a tree-like display NOTE: this is a brute-force implementation with no attempts at optimization. But it's a very simple tree+table implementation.
JComponentRecorder: Record basic semantic events you might find on an JComponent. Watches for events that trigger an action from the component's action map. As of 1.3.1, KEY_TYPED and KEY_RELEASED events can trigger an action.
EventRecorder: Provides recording of raw AWT events and high-level semantic events. This is the main controller for any SemanticRecorder objects. Typing Shift-ESC will terminate the recording (no cancel action is available).
JComboBoxRecorder: Record basic semantic events you might find on an JComboBox. Select a value (not done) Enter a value (if editable) (not done) FIXME may need to pop off LAF components for recorder
TextField: A better text field that fires when focus leaves the component, and also selects all the contents when the action is fired to indicate the contents were accepted.
ScriptEditorFunctionalSuite: Provides aggregation of all scripts for testing the Script Editor. Assumes tests are available in a subdirectory "test/scripts/editor".
JTableRecorder: Record basic semantic events you might find on an JTable. Click one or more times in a cell
JTreeRecorder: Record basic semantic events you might find on an JTree. Click one or more times in a cell
AbstractButtonRecorder: Record basic semantic events you might find on an AbstractButton. This class handles a click on the button.
JTabbedPaneRecorder: Record basic semantic events you might find on an JTabbedPane. Select a tab.
ComponentBrowser: Browse an existing component hierarchy. Thanks to the JFCUnit guys for the basis for this code.
JMenuItemRecorder: Override AbstractButton behavior, since we expect to grab a menu selection instead of a click.
JListRecorder: Record basic semantic events you might find on an JList. Select a cell
XMLEditor: An editor for an XMLifiable object. It'd be nice to provide a real XML editor here...
| Home | Contact Us | Privacy Policy | Terms of Service |