I see that you change the code of protected void notify(final int
eventType, final Event createEvent, final Widget widget) {}
in abstractswtbot.java which sleeps for a given time and gets back
earlier it was running a sync thread
don't you think sleep is non-deterministic? if on some wizard i have a
button that i click which invokes a series of operations which can
potentially take minutes ( for example retrieving something from a server )
then i'd have to guess the time that it should sleep for before asserting
something in my non-ui thread
the workarounds would be that I wait in the non-ui thread till some
condition is true.
any better solution for this. if SWTbot has to replicate what the user sees
then the click() should return only when its done. this was happening when
the notify(){} code had a sync thread at the end.
thoughts?
On Thu, Jul 10, 2008 at 6:29 PM, Somesh Sasalatti <[EMAIL PROTECTED]>
wrote:
> hmm.. i keep hitting some freaking short cut that sends the
> mail....anyways..continuing.... this is the real version
>
> Hi,
>
> I currently have 3.3.1.1 running with the released version of swtbot and
> things work fine.
>
> however, if I use 3.3.2 with released version, tests don't run because
> apache.commons.logging.x jar that is with the swtbot plugin conflicts with
> what is already there in eclipse. It might be a good idea to remove this.
>
> if I use 3.3.2 with the nightly, the logging problem goes away but tests
> fail on several accounts
> 1) bot.table.select("something") used to simulate a double click in 3.3.1
> and in 3.3.2 only selects it.
> 2) bot.button("finish").click() on a wizard clicks the finish button but
> doesn't wait for the click operation to finish. here's an example.
> the pseudo code goes like this:
> open the wizard.
> fill in what you need.
> bot.button("finish").click();
> assert( project exists)
>
> now previously in 3.3.1 with the released plugin the assert would not
> execute till the bot.button("finish").click(); finished but in 3.3.2 with
> the latest nightly, it doesn't seem to wait. so if it takes a while to
> create the project, the assert will fail.
>
> any ideas on what's happening.
> swt changed? 3.3.2 handles something differently ?
> bug in nightly?
>
>
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
SWTBot-users mailing list
SWTBot-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/swtbot-users
http://swtbot.org/ - a functional testing tool for SWT/Eclipse
