We are in the process of creating (actually porting) some old apps to
Eclipse plugins. We are building the eclipse plugins via Cruise Control
and have our version control system in Clearcase. We have after reading (
http://www.eclipse.org/articles/Article-PDE-Automation/automation.html )
managed to figure out how to exceute an Junit plugin test via cruise
control as an normal command task just. Great now our plugins can be
tested !
The next caveat is to try and get coverage of the Junit plugin tests. How
does the developers involved in Eclipse.org do this currently, do every
developer run their own coverage tools to improve the coverage rate, or is
there some magical tool that goes through all junit plugin tests and runs
those aginst the plugins to measure the coverage?
We have now gone through Nounit, and Cobertura with trying to set this up
to measure test code coverage to no sucess. We can get Cobertura/Nounit to
report back on things that are normal Junit tests, but not junit plugin
tests, thus our coverage is very low.
I guess our last hope is to try Emma (http://emma.sf.net) seems soemone
has had luck with this at least
(http://dev.eclipse.org/newslists/news.eclipse.platform/msg44478.html)
unless there is some documentation for how to set this up for Eclipse
plugin tests. We have profiled the Junit plugin test via TPTP and that
works but it does not give us the line / branch coverage that we would
want, also we want to excecute it from cruise control (headless) on a
regular basis.