db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Monitoring/improving code coverage (was Re: code coverage results for trunk - svn revision no 390306)
Date Mon, 03 Apr 2006 21:16:36 GMT
David W. Van Couvering wrote:

> Did I ask this before?  Do we want to agree upon a "low water mark"
> for code coverage and send out a "Quality Regression" email if our
> testing coverage falls below that mark?  I think this would have a lot
> of value.

This sounds like an interesting idea.   Code coverage is an important
quality data point.  What kind of granularity would it have?  Would it
be just the overall number or would individual packages or files be
flagged?   Also for areas that have poor coverage, how could we
encourage numbers to be brought up before or during enhancements?


View raw message