Here are the new findings: On 01-Jul-08, at 11:56 AM, Ketan Padegaonkar wrote:
>> 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. All unit tests for eclipse plugins fail. Tests run on the UI thread, and dialogs that have an event loop inside them block the execution of tests. Hans have you seen this behavior ? >> 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. I'm reverting to the previous revision where at which the patch was applied. The details of the change and the patch can be found here for future reference: http://fisheye3.atlassian.com/changelog/swtbot/?cs=815 -- 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
