Provides basic elements for constructing a test script. A
{@link abbot.script.Step} is the basic unit of execution. Steps may be
grouped into a {@link abbot.script.Sequence}. See the documentation for
{@link abbot.script.Step} for information on extending script features.
Following are some of the basic elements of a {@link abbot.script.Script}:
- Invoking Code
Usually you will have a single Launch step at the beginning of your script
to load and activate your GUI under test. See the Launch class for details.
- Component Reference
This entry is not an actual script step, but a representation of an actual
component within the GUI. The ComponentReference ID may be used in argument
lists where a java.awt.Component would normally be expected. See the
{@link abbot.script.ComponentReference} class for details.
- Action
This type of step invokes a semantic user action on the GUI, such as a mouse
clickk, menu selection, or drag/drop action. Different actions are
supported by different GUI components. All actions supported may be found
in the APIs for the
{@link abbot.tester.ComponentTester} and its
subclasses.
See the {@link abbot.script.Action} class for details.
- Assert
This type of step tests for a condition in the GUI, such as whether a
Component property matches a particular value, or it might invoke a custom
test exported by a ComponentTester class. See the Assert class for details.
- Wait
This type of step simply waits for an Assert to become true, with an
adjustable timeout and sleep cycle. See
{@link abbot.script.Assert#setWait(boolean)} for details.