I'm not sure I understand the report. For example I was looking at the
org.jboss.as.ejb3 package
http://www.qa.jboss.com/~ozizka/coverage-report/html/org.jboss.as.ejb3/in....
That looks very odd. It seems to be reporting just 6 (mostly of low
relevance) classes from that package. Is this some config issue with the
reporting? Certainly the testsuite would have covered a lot more classes
in the org.jboss.as.ejb3 package.
-Jaikiran
On Wednesday 25 January 2012 02:39 AM, Ondrej Zizka wrote:
Hi,
this is the first AS 7 coverage report:
http://www.qa.jboss.com/~ozizka/coverage-report/html/index.html
<
http://www.qa.jboss.com/%7Eozizka/coverage-report/html/index.html>
Download at:
http://www.qa.jboss.com/~ozizka/AS7-coverage-full-2012-01-24.zip
<
http://www.qa.jboss.com/%7Eozizka/AS7-coverage-full-2012-01-24.zip>
Jira:
https://issues.jboss.org/browse/AS7-2022
It's made using the JaCoCo tool.
Whole testsuite was run, except for the integration/compat module.
Only tests launched through Arquillian are counted. Thus, for example,
CLI tests are not - since they launch JVM on their own.
To be addressed later.
Please look at your modules/components (both devs and QA) and take
actions to increase the coverage.
If your tests are not being counted, please let me know, and we will
figure out how to fix it.
Regards,
Ondra
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev