[TIP] detecting when a changeset is not well tested

[Tarek Ziadé]

On Tue, Aug 23, 2011 at 5:56 PM, Michael Foord <michael at voidspace.org.uk> wrote:
> On 23/08/2011 15:59, 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 don't know of a tool like that, but I'd be very interested in one. :-)

In theory it should be easy to build. And even to output a graphviz
trending, I'll give it a shot :D


> Michael
>
>>
>> I guess that could be a script on the top of "coverage", but maybe
>> someone has done this already ?
>>
>> Cheers
>> Tarek
>>
>
>
> --
> http://www.voidspace.org.uk/
>
> May you do good and not evil
> May you find forgiveness for yourself and forgive others
> May you share freely, never taking more than you give.
> -- the sqlite blessing http://www.sqlite.org/different.html
>
>



-- 
Tarek Ziadé | http://ziade.org