Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331219 - Re-instate code coverage checks
Summary: Re-instate code coverage checks
Status: CLOSED DUPLICATE of bug 325871
Alias: None
Product: Virgo
Classification: RT
Component: virgo-build (show other bugs)
Version: 2.1.0.RELEASE   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 3.7.0.M02   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 331221
Blocks: 333258
  Show dependency tree
 
Reported: 2010-11-26 10:38 EST by Glyn Normington CLA
Modified: 2016-07-05 04:06 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2010-11-26 10:38:53 EST 
The Clover code coverage tool is available free to open source projects. Before donation to Eclipse, builds ran code coverage checks using Clover and failed if the coverage fell below a pre-defined value. This should be re-instated for Virgo.
Comment 1 Glyn Normington CLA 2010-12-22 05:06:40 EST 
As reported in bug 331221 only open source tools are allowed on the Eclipse Hudson CI server, so we will not be able to get code coverage checks as part of Eclipse Hudson CI builds unless we can identify an open source replacement for Clover.

Emma is an Eclipse plugin and I do not know whether it is possible to run it as part of a build to gather the necessary coverage stats.
Comment 2 Chris Frost CLA 2010-12-22 05:25:46 EST 
There is a plugin for Emma on Hudson (http://wiki.hudson-ci.org/display/HUDSON/Emma+Plugin) but we would have to convince the Webmaster to install it. It is also possible to just run Emma from the ant build but we would then have to go and look at the coverage results for each build. With the plugin we would get nice trend graphs in the Hudson UI.
Comment 3 Glyn Normington CLA 2010-12-22 05:39:30 EST 
That's interesting. Unfortunately what we really want is to know when the code coverage of runtime (non-test) code by unit tests drops below the configured threshold. Eye-balling coverage results or trend graphs won't give us that, so we'd have to find some way of processing Emma's output.
Comment 4 Florian Waibel CLA 2015-06-03 07:48:19 EDT 
With Bug 325871 we have a coverage check up and running now.

*** This bug has been marked as a duplicate of bug 325871 ***
Comment 5 Florian Waibel CLA 2016-07-05 04:06:20 EDT 
3.7.0.M02 has been shipped.