Re: [Cobertura-devel] Couple newbie questions

[John W. L. <Joh...@sa...>]

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?