[TIP] detecting when a changeset is not well tested

Nicolas Chauvat nicolas.chauvat at logilab.fr
Wed Aug 24 07:06:14 PDT 2011


On Wed, Aug 24, 2011 at 01:11:19PM +0100, Michael Foord 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.

Sounds sensible. I added a feature request for our cubicweb-forge tool
that already includes continuous integration, code review and code
coverage, but has not linked review and coverage yet. :)

Nicolas Chauvat

logilab.fr - services en informatique scientifique et gestion de connaissances  

More information about the testing-in-python mailing list