[
https://issues.jboss.org/browse/AS7-2022?page=com.atlassian.jira.plugin.s...
]
Rostislav Svoboda edited comment on AS7-2022 at 1/12/12 7:00 AM:
-----------------------------------------------------------------
Current Cobertura based coverage jobs mentioned in description are for AS7 unit tests.
Cobertura needs source codes to produce instrumented classes and jars. And it has problems
when tests are in separate module and not in the same module as source codes.
I was using Cobertura and Emma for code coverage on WS which has its testsuite in separate
module and 2 submodules. I started with Cobertura and spent quite a lot of time to patch
pom files. Than I had to merge Cobertura report files and it's not supported in maven
plugin. I had to call ant from maven to merge these files and I had to know their exact
location.
Conclusion: Cobertura is good choice for code coverage for unit tests in modules but not
good for testsuite module.
I'm using Emmma for WS code coverage. It can instrument directly jars, source code are
not necessary. My workflow is simple: instrument jars in AS, patch pom.xml for
emma.rt.control.port, run tests and generate report. There are some problems (for example
with emma.rt.control.port) but it's minor comparing problem with Cobertura.
Conclusion: Works for my use use-case. Should work for your too.
Examples:
-
https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbos...
-
https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbos...
was (Author: rsvoboda):
Current Cobertura based coverage jobs mentioned in description are for AS7 unit tests.
Cobertura needs source codes to produce instrumented classes and jars. And it has problems
when tests are in separate module and not in the same module as source codes.
I was using Cobertura and Emma for code coverage on WS which has its testsuite in separate
module and 2 submodules. I started with Cobertura and spent quite a lot of time to patch
pom files. Than I had to merge Cobertura report files and it's not supported in maven
plugin. I had to call ant from maven to merge these files and I had to know their exact
location.
Conclusion: Cobertura is good choice for code coverage for unit tests in modules but not
good for testsuite module.
I'm using Emmma for WS code coverage. It can instrument directly jars, source code are
not necessary. My workflow is simple: instrument jars in AS, patch pom.xml for
emma.rt.control.port, run tests and generate report. There are some problems (for example
with emma.rt.control.port) but it's minor comparing problem with Cobertura.
Conclusion: Works for my use use-case. Should work for your too.
Examples:
-
https://hudson.qa.jboss.com/hudson/view/EAP6-jbossws/job/eap6-jbossws-emm...
-
https://hudson.qa.jboss.com/hudson/view/EAP6-jbossws/job/eap6-jbossws-emm...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira