FrameFixture.robot.click(target) and robot.click(FrameFixture.target) do not act the same, nor at the same speed

_Issue by **[Teague Bick](http://jira.codehaus.org/secure/ViewProfile.jspa?name=tabgok)** from Wed, 9 Feb 2011 13:50:02 -0600_
_Originally opened as http://jira.codehaus.org/browse/FEST-428_

---

window.robot.click(...), for example:

window.robot.click(window.menuItem("File Menu").target);

window.robot.click(window.menuItem("Open Project").target);

is so much faster than (window.component(...).click), for example:

window.menuItem("File Menu").click();

window.menuItem("Open Project").click();

In addition, they suffer from slightly different functionality. I placed both methods in a loop to click a menu item 50 times:

for(int i=0;i<50;i++){

robot.click( window.menuItem(new GenericTypeMatcher<JMenu>(JMenu.class){

protected boolean isMatching(JMenu item)

{
return "File".equals(item.getText());
}

}).target);

}



for(int i=0;i<50;i++){

window.menuItem(new GenericTypeMatcher<JMenu>(JMenu.class){

protected boolean isMatching(JMenu item){
return "File".equals(item.getText());
}

}).click();

}

The first loop is faster and will repeatedly open / close the "File" menu, while the second loop is slower and freezes after selecting the MenuItem twice.

---

votes (original issue): 0
watches (original issue): 0

Inizia riproducendo i due loop usando FrameFixture.robot.click(...target) e FrameFixture component.click(), inclusi gli esempi di GenericTypeMatcher. Traccia i due punti di ingresso di click e confronta i relativi tempi e il comportamento dei menu; il lavoro è completato quando entrambe le forme si comportano in modo coerente senza il freeze segnalato, con copertura di regressione per il caso di clic ripetuti.

Scritto dal modello di indicizzazione a partire dal testo della issue.