FYI, I have set this up in Hudson. Note that this does *not* run
periodically since it is slow, but those of you with necessary
privileges on Hudson can manually kick off a code coverage run
whenever you feel it is necessary.
http://hudson.qa.jboss.com/hudson/job/jbosscache-core-trunk-code-coverage/
Here are the results of the latest run:
http://hudson.qa.jboss.com/hudson/job/jbosscache-core-trunk-code-coverage...
Cheers,
Manik
On 28 May 2008, at 17:43, Manik Surtani wrote:
I've added EMMA code coverage to the JBC support POMs. This is
disabled by default since it entails adding interceptors to tests
and makes the test suite run slower than usual. Instead it can be
run manually whenever new features are added or there are
significant code changes, etc. to ensure we have a decent level of
code coverage.
This is formally a part of jbosscache-common 1.3, but recent 1.3-
SNAPSHOT versions have this as well.
You can enable it by specifying the "codeCoverage" profile. If you
run the "site" goal, it will generate HTML reports based on the
tests run.
E.g.,
$ mvn site -PcodeCoverage
will run the default test suite (tests in the "unit" group in
jbosscache-core, for example, or "functional" in jbosscache-pojo).
In jbosscache-core, other test suites can be selected by specifying
the necessary profile.
E.g.,
$ mvn site -PcodeCoverage,test-functional
Please see README-Maven.txt for more details.
Reports are in
target/site/index.html
which has links to EMMA code coverage reports, etc.
Enjoy!
Manik
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org