Finally I solved my threading problem. You remember, we have to backport SWT
Bot to RCP and Eclipse 3.2. The hardest thing for me has been to backport the
Eclipse plugin which starts the JUnit Plug-in Tests in a non-UI thread. I
nearly managed to do it when I found an easier solution in my eyes.
I "stole" it from the free Abbot SWT. Maybe you like it. To me, it has several
advantages compared to the Eclipse plugin solution:
- more easy to understand
- more straightforward to debug
- standard way to automate it (exactly like any other ordinary JUnit Plug-in
Test)
- probably less maintainance work
- much more compatible to various Eclipse versions
One side effect is that users need to extend from this class instead of
TestCase or any other class. I don't know currently how that solution would
look like for JUnit 4.x.
Here is the code if you like it:
http://paste-it.net/public/l3a23e2
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/swtbot-users
http://swtbot.org/ - a functional testing tool for SWT/Eclipse
