> 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.
Most SWTBot unit tests run fine, I've not looked at the plugin tests for now, and will do so today. > So: > 1. How should this be run? This should now be run as regular JUnit tests (or JUnit plugin tests) for plugins/rcp apps. > 2. Why is this change being made? 1. The launcher configuration need not be maintained anymore -- this used internal API in PDE and JDT. 2. The API was not backward compatible which meant that some users like Hans had to do some workarounds for 3. Lesser confusion in the minds of people starting with SWTBot, we've all seen a slew of questions from starters. 4. There's no need to run tests in a non-UI thread, tests are intelligent enough to run themselves in the non-UI thread. > Should it be reverted? The new approach is a very good approach (thanks to Hans) and if things break badly, we could take some efforts to fix this, rather than a slew of questions from newbies. We could definitely revert this if things break *way* too much to a point where this is not repairable. -- 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
