[TIP] detecting when a changeset is not well tested

[Pere Martir]

On Tue, Aug 23, 2011 at 4:59 PM, Tarek Ziadé <ziade.tarek at gmail.com> wrote:
> 1/ keep a history of the test coverage for every module of my project
> 2/ on a commit, detect when the coverage for a module lowers
> 3/ send a warning and point the part that's not covered

This is probably the functionality of a CI server than a test framework ?

See:

"Gcov Coverage Reports in Jenkins"
- http://www.semipol.de/archives/320