Examples of abbot.tester.ComponentTester$AWTMenuListener

abbot.tester.ComponentTester
Provides basic programmatic operation of a Component. Also provides some useful assertions about properties of a Component.
Actions are generally user-driven actions such as menu selection, table selection, popup menus, etc. All actions should have the following signature:
public void actionWhat(Component c, ...);
It is essential that the argument is of type Component; if you use a more derived class then the actual invocation becomes ambiguous since method parsing doesn't attempt to determine which identically-named method is the most-derived. NOTE: All actions should ensure that the actions they trigger are finished or will be finished before subsequent operations before returning.
Assertions are either independent of any component (and should be implemented in this class), or take a component as the first argument, and perform some check on that component. All assertions should have one of the following signatures:
public boolean assertWhat(...);
public boolean assertWhat(Component c, ...);
Note that these assertions do not throw exceptions; normally these assertions will be wrapped by an abbot.script.Assert step if you want to cause a test failure, or you can manually throw the proper failure exception.
Property checks may also be implemented in cases where the component "property" might not be readily available or easily comparable, e.g. see JPopupMenuTester.getMenuLabels().
public Object getProperty(Component c);
public boolean isProperty(Component c);
Be careful not to name any support methods with the property signature, since these are scanned dynamically to populate the editor's action menus.
There are two sets of event-generating methods. The internal, protected methods inherited from abbot.tester.Robot are for normal programmatic use within derived Tester classes. No event queue synchronization should be performed except when modifying a component for which results are required for the action itself.
The public actionX functions are meant to be invoked from a script or directly from a hand-written test. These actions are distinguished by name, number of arguments, and by argument type. The actionX methods will be synchronized with the event dispatch thread when invoked, so you should only do synchronization with waitForIdle when you depend on the results of a particular event prior to sending the next one (e.g. scrolling a table cell into view before selecting it).
The ComponentLocation abstraction allows all derived tester classes to inherit click, popup menu, and drag variants without having to explicitly define new methods for component-specific substructures. The new class need only define the parseLocation(String) method, which should return a location specific to the component in question.
Derive from this class to implement actions and assertions specific to a given component class. Testers for any classes found in the JRE (i.e. in the java.awt or javax.swing packages) should be in the abbot.tester package. Extensions (testers for any Component subclasses not found in the JRE) must be in the abbot.tester.extensions package and be named the name of the Component subclass followed by "Tester". For example, the javax.swing.JButton tester class is abbot.tester.JButtonTester, and a tester for org.me.MyButton would be abbot.tester.extensions.MyButton.
Add-on tester classes should set the following system properties so that the actions provided by their tester can be properly displayed in the script editor. For an action "actionWiggle" provided by class abbot.tester.extensions.ExtendedTester, the following properties should be defined:
- actionWiggle.menu short name for Insert menu
- actionWiggle.desc short description (optional)
- actionWiggle.icon icon for the action (optional)
- ExtendedTester.actionWiggle.args javadoc-style description of method, displayed when asking the user for its arguments
Since these properties are global, if your Tester class defines a method which is also defined by another Tester class, you must supply the class name as a prefix to the property.
Note on method naming conventions
Action methods should be named according to the human-centric action that is being performed if at all possible. For example, use actionSelectRow in a List rather than actionSelectIndex. If there's no common usage, or if the usage is too vague or diverse, use the specific terms used in code. For example, JScrollBarTester uses actionScrollUnitUp and actionScrollBlockUp; since there is no common language usage for these concepts (line and page exist, but are not appropriate if what is scrolled is not text).
When naming a selection method, include the target of the selection in the name (e.g. JTable.actionSelectCell), since some components may have more than one type of selectable item within them.

            }
        }
        // Scan the corresponding component tester for additional property
        // methods 
        try {
            ComponentTester tester = componentClass != null
                ? ComponentTester.getTester(componentClass)
                : (ComponentTester)testerClass.newInstance();
            Iterator iter = getComponentTesterMethods(tester).iterator();
            while (iter.hasNext()) {
                Method m = (Method)iter.next();

View Full Code Here

        }
        assertTrue("Annotation should not automatically close",
                   ann.isShowing());
        assertTrue("Annotation should block execution while displaying",
                   ann.isRunning);
        ComponentTester tester = new ComponentTester();
        Component button =
            getFinder().find(w, new ClassMatcher(JButton.class));
        tester.actionClick(button);
        // Give the annotation thread time to clean up
        Timer timer = new Timer();
        while (ann.isShowing()) {
            getRobot().sleep();
            if (timer.elapsed() > 1000)

View Full Code Here

                processed.put(methods[i].getName(), methods[i]);
            }
        }
        // Now look up propert accessors provided by the corresponding
        // ComponentTester class.
        ComponentTester tester = ComponentTester.getTester(cls);
        methods = tester.getPropertyMethods();
        for (int i=0;i < methods.length;i++) {
            if (!processed.containsKey(methods[i].getName())) {
                // Properties provided by the ComponentTester are never
                // filtered. 
                processed.put(methods[i].getName(), methods[i]);

View Full Code Here

        final JTextField tf = new JTextField();
        tf.setColumns(10);
        KeyWatcher kw = new KeyWatcher();
        tf.addKeyListener(kw);
        showFrame(tf);
  ComponentTester tester = new ComponentTester();
  tester.actionFocus(tf);
        int code = KeyEvent.VK_ESCAPE;
        int mods = 0;
  tester.actionKeyStroke(code, mods);
        assertTrue("Never received key press", kw.gotPress);
        assertTrue("Never received release", kw.gotRelease);
        assertEquals("Wrong key code", code, kw.code);
        assertEquals("Wrong modifiers", mods, kw.modifiers);
    }

View Full Code Here

            KeyEvent.VK_CAPS_LOCK,
            KeyEvent.VK_NUM_LOCK,
            KeyEvent.VK_SCROLL_LOCK,
            KeyEvent.VK_KANA_LOCK,
        };
  ComponentTester tester = new ComponentTester();
        for (int i=0;i < CODES.length;i++) {
            try {
                boolean state = Toolkit.getDefaultToolkit().
                    getLockingKeyState(CODES[i]);
                try {
                    tester.actionKeyStroke(CODES[i]);
                    boolean state2 = Toolkit.getDefaultToolkit().
                        getLockingKeyState(CODES[i]);
                    assertEquals("Reported state of locking key '" + KEYS[i]
                                 + "' did not change",
                                 !state, state2);
                }
                finally {
                    tester.actionKeyStroke(CODES[i]);
                }
            }
            catch(UnsupportedOperationException e) {
                // ignore
            }

View Full Code Here

TOP

Related Classes of abbot.tester.ComponentTester$AWTMenuListener

abbot.BugReport

abbot.editor.ComponentPropertyModel

abbot.editor.editors.PropertyCallEditor

abbot.finder.matchers.WindowMatcher

abbot.script.AnnotationTest

abbot.util.BugsTest

java.lang.reflect.Method

javax.swing.JMenuItem

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.