WebSphere cannot start webapp instrumented by cobertura

Question

I instrumented a few classes, packed them in war and ear. Install this ear in WebSphere. Now this Application Status is Stopped. Should I place cobertura.jar anywere? Is where my mistake?

You're more likely to get productive responses if you can provide some more detail about your problem, possibly the code which isn't working. Without more detail it's hard for potential answer-ers to help out. — ASGM, Mar 03 '13 at 18:56

score 1 · Answer 1 · edited Dec 29 '13 at 05:19

Websphere Application server allowes ear to be deployed/installed, so build you application ear with cobertura instrumented classes.
Copy the cobertura.ser file generated by default in target/cobertura/cobertura.ser location in your system while maven build, in to ../AppServer/profiles/AppSrv01/ location of WAS.
Start the server
run some testes.
Stop the server. cobertura.ser will get updated.

Run the cobertura report.

score 0 · Answer 2 · answered Mar 05 '13 at 11:10

0

I solve a lot of my problem while read this doc: http://mojo.codehaus.org/cobertura-maven-plugin/instrumentingDeploymentArtifact.html

Found my cobertura.ser in /ibm/was/profiles/profile/

answered Mar 05 '13 at 11:10

VovecUdalec

151
1
8

score -1 · Answer 3 · answered Mar 04 '13 at 05:18

Cobertura instruments classes to be able "to identify which parts of your Java program are lacking test coverage"

I think it adds its own classes so they collect the information and at the end of the test coverage phase write this down to a data store. With that said, I'd expect cobertura.jar and some other jars should be included in the webapp's WEB-INF/lib directory.

To get more insights on the issue, have a look at SystemOut.log of the server instance. It's in [WEBSPHERE_HOME]/profiles/[PROFILE_NAME]/logs/server1 directory.

WebSphere cannot start webapp instrumented by cobertura

3 Answers3