Take a look at the Typer (can't remember what the class is called) used by the DefaultWindowWrapper. I added a listener to the events which hangs until it receives it, then waits for the event queue to empty. One would hope that would mean that other listeners had, by then, also been informed.
Unfortunately, sometimes the Typer's listeners aren't getting the posted events _at all_ on Ubuntu, so they're timing out. Haven't worked out why that's the case. I haven't added this checker to the button clicks yet, but can do so. Any chance we can check I've fixed it on your Mac? Cheers, Liz. -- Elizabeth Keogh [EMAIL PROTECTED] http://www.livejournal.com/users/sirenian "Carlos Villela" <[EMAIL PROTECTED]> wrote on 16/01/2007 20:51:37: > Hey gang, > > I've noticed the build's been failing on my iBook G4, like this: > > [run behaviours] 1) DefaultWindowWrapper should click a button on a window: > [run behaviours] VerificationException: Expected at least 1 calls but > got 0 for actionListener.actionPerformed[anything]: > (...) > at org.jbehave.core.minimock.UsingMiniMock.verifyMocks(UsingMiniMock.java:63) > at org.jbehave.threaded.swing.DefaultWindowWrapperBehaviour. > shouldClickAButtonOnAWindow(DefaultWindowWrapperBehaviour.java:50) > (...) > > Apparently, putting a Thread.sleep(500) around line 45 in > DefaultWindowWrapperBehaviour fixes it - but I know this is far from > acceptable. > > Any ideas on how to go about it? > > Cheers, > > - Carlos > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email >
