Problems when Enabling Code Coverage

This is more a warning for anyone looking to use builtin code coverage with their system.

We deploy a web application as part of our build process and then run tests against it. When I enable the code coverage for a build, the webapp stops deploying as references to Emma classes remain unresolved.

Basically, enabling code coverage may not be a completely transparent action and may need some plumbing in the build to handle.

One question with this. Is there any way from within our build to easily determine if code coverage has been enabled? Can we look at any properties which are set to trigger handling as needed for the build?

--Tim

1 comment
Comment actions Permalink

Tim McNerney wrote:

This is more a warning for anyone looking to use builtin code coverage with their system.

We deploy a web application as part of our build process and then run tests against it. When I enable the code coverage for a build, the webapp stops deploying as references to Emma classes remain unresolved.

Basically, enabling code coverage may not be a completely transparent action and may need some plumbing in the build to handle.

One question with this. Is there any way from within our build to easily determine if code coverage has been enabled? Can we look at any properties which are set to trigger handling as needed for the build?


Surely there is a way.
When coverage is enabled, there is a system property "report.html.out.file".

Hope this helps,
KIR

P.S. FAQ has been updated ;)


--Tim



--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.