Re: [Cobertura-devel] Couple newbie questions

[Mike M. <mi...@ho...>]

Thanks for the quick response.   So what do most people do for #2 below?   Separate compiles and jar/war/ear creation or can you do something like instrumenting the jars/wars/ear that you deploy to the app server and then just use the original copy of the jars, etc from their build destination folder when you package the project/product?
 
Our full build with test cases and installer creation currently takes about 1 1/2 hours so my preference to limit keep the time down but still get the benefit of having/providing code coverage reports.
 


From: Joh...@sa...
To: mi...@ho...; cob...@li...
Subject: RE: [Cobertura-devel] Couple newbie questions
Date: Tue, 28 Sep 2010 21:15:34 +0000






 
1)      Yes
2)      Yes.
3)      Yes.
 


From: Mike Miller [mailto:mi...@ho...] 
Sent: Tuesday, September 28, 2010 5:11 PM
To: cob...@li...
Subject: [Cobertura-devel] Couple newbie questions
 
I used Cobertura shortly several years ago on a web application and now I want to provide code coverage reports for my current project.  This is a large project using either JBoss or Weblogic with a lot of EJBs.  I wanted to clarify a couple things before I got down making all of the build updates:


1) the general process/steps are compile,instrument, deploy and then report?

2) If the steps above are correct, doesn't that leave me with an instrumented version of my code-base once the build is completed? Trying to figure out if I need to create a full set of non-instrumented jars, wars, and ear and also a full set of instrumented jars, wars, and ear because the deployment artifacts from our nightly build are also used to create our InstallAnywhere build package. I don't believe I want to run into the case where my build uses the instrumented files as part of the installer package being built!

3) Our current JUnit tests are a combination of true JUnit testcases along with 'integration JUnit testcases' which exercise the EJB services from a client perspective.   I assume this means that I will probably get 'sets' of .SER files, one from the client side and one from the server (once I stop JBoss or WLS).    Do I then run the merge to create a unified .SER file and then generate the report from that unified SER?