Ketan,
I tried it out and now I can't run any tests. I tried running my older Run
Configuration that worked before the upgrade (SWTBot Runner, JUnit 3). That
failed with an illegal Thread acess excpetion. Then I created a new run
configuration using the JUnit Plugin Tests. Setup for Junit 3 and that just
reports terminated before even running.
So:
1. How should this be run?
2. Why is this change being made? Should it be reverted?
steve
On Mon, Jun 30, 2008 at 2:12 PM, Ketan Padegaonkar <
[EMAIL PROTECTED]> wrote:
> I've made some major changes with SWTBot which do not require tests to
> run in a non-UI thread.
>
> This could have major repercussions for users. I'd encourage users to
> try out the latest version of SWTBot available at
> http://swtbot.sourceforge.net/artifacts/trunk/
> and write back if you find any issues.
>
> -- Ketan
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> 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
>
>
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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
