[TIP] detecting when a changeset is not well tested

Tarek Ziadé ziade.tarek at gmail.com
Tue Aug 23 09:29:30 PDT 2011

On Tue, Aug 23, 2011 at 6:12 PM, Ned Batchelder <ned at nedbatchelder.com> wrote:
> On 8/23/2011 10:59 AM, Tarek Ziadé wrote:
>> Hey
>> So, I can build this in a script or... ask here if something exists
>> already :)
>> I am looking for a script that can:
>> 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
>> I guess that could be a script on the top of "coverage", but maybe
>> someone has done this already ?
> I don't know of something like this, but I've heard requests like this
> before, and would be interested to help support it.  For example,
> coverage.py could have a reporting mode where it reported on coverage
> deltas: red for coverage lost, green for coverage gained.

Right. Also, keeping in this mode the % would be nice to be able to
draw trending diagrams

> Then your script
> could manage the archiving of coverage data, and present two samples for
> delta reporting.

Yes, sounds like a plan.

I can try to contribute this, will look at the reporting at coverage


> --Ned.
>> Cheers
>> Tarek

Tarek Ziadé | http://ziade.org

More information about the testing-in-python mailing list