On 05-Jun-08, at 11:58 PM, Somesh Sasalatti wrote: > In the meanwhile, is it not possible to run a test in junit plugin > test-headless mode and launch a workbench( ui thread) instead of > creating a custom swtbot launch config.
A JUnit launch is far different from a simple java launch, where eclipse adds itself as a listener so that you can see updates in the junit view, throw PDE into this mix and things get complex really quick. You *could* possibly look at the JVM arguments of a JUnit plugin launch and try to perform a java launch with the same/similar arguments. You'll however not get notifications of test execution in the JUnit view, and may need to figure out alternative reporting mechanisms. I'd personally recommend running a command line build where you can do all the fancy instrumentation that you ever wanted to and get all the reports after a test run. On another note, I'm not sure if code coverage by executing functional tests is a good idea. Functional test coverage should be the number of scenarios that you've got automation for against the number of scenarios that have been developed. Cheers, Ketan Padegaonkar, I blog... therefore I am... http://ketan.padegaonkar.name 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
