Hi guys,
thought you might be interested in this.
Let's say you're writing SWT tests. You need to launch these tests as SWTBot
tests in eclipse as tests are run in a non ui thread and that non ui thread
spawns a workbench.
Now, let's say you want to instrument your to-be-tested-code with clover and
see what code does your swtbot test hits.
If you install the clover plugin, you'll see that it only supports the
standard config types of Eclipse application, junit, junit-plugin test etc.
in our case we have a new one, SWTBot test config....What do we do!!
Simple( well not so simple...i got help from clover for this)
add this to your VM argument in the argument tab.
-Xbootclasspath/a:<full path to clover runtime jar>
for ex.
-Xbootclasspath/a:/home/ssasalatti/eclipse/plugins/com.cenqua.clover.runtime_2.3.1.v20080602190340/clover-runtime.jar
assuming that your to-be-tested code is already instrumented with clover;
when you run your test, you'll see your coverage numbers.
Clover is looking into how they can better support for non-standard launch
configuration types.
Thanks
Somesh
-------------------------------------------------------------------------
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
