Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Ticket #3882 (new enhancement)

Opened 8 years ago

Last modified 8 years ago

Create a Blame Coverage plugin

Reported by: jdsiiro Owned by: jdsiiro
Priority: normal Milestone:
Component: Hudson Version:
Keywords: Cc: wehart

Description

From Bill:

While chatting about coding metrics today, a cool idea occurred to me. We could annotate code coverage with user commit id's to generate a 'blame' report that provide statistics of how many lines each developer has committed that are not covered by unit tests.

I think that this would be a very useful tool for encouraging developer enthusiasm for tests to ensure code coverage...

This sounds like a generic extension of Hudson's current Cobertura plugin???

Attachments

Change History

comment:1 Changed 8 years ago by anonymous

Careful! This may lead to perverted tests. A tests that execute the code but don't do assertions. Also some tricky code that is hard to test may be punished, i.e. error conditions.
Errors can be mocked up, but in lots of cases it's not worth the effort.

It may be okay to overlay the information on the source code.
For reasons mentioned above I think publishing statistics without context could be harmful.

comment:2 Changed 8 years ago by wehart

But these concerns are generally applicable to coverage metrics. You don't know whether coverage was 'just executed' or 'executed with tests'. Also, the hard-to-test cases are just a general problem for coverage metrics.

But having said this, the reality is that some developers are happy to write code without including any testing. This metric would highlight that behavior.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.