[TIP] detecting when a changeset is not well tested

[Augie Fackler]

On Wed, Aug 24, 2011 at 7:11 AM, Michael Foord <michael at voidspace.org.uk> wrote:
> On 24/08/2011 11:14, Nicolas Chauvat wrote:
>>
>> Hi,
>>
>> On Tue, Aug 23, 2011 at 09:15:02PM -0500, Augie Fackler wrote:
>>>
>>> This is also the kind of thing I'd love to see integrated with a code
>>> review tool, FWIW.
>>
>> How do you see it working? Care to provide a couple scenarios / use
>> cases ?
>>
> It seems pretty obvious. Alongside the diff is a report on how the diff
> changes the test coverage of the modules it touches. A code review tool
> would need access to the coverage reports of course - which means either
> they need to be checked in, or the code review tool needs access to a CI
> server.

Or your tool for posting to the review server could include the
coverage reports with the diff upload.

>
> All the best,
>
> Michael Foord
>
> --
> 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
>
>