Unhooked test suites

[David Cheney]

Yup. I'm working with the gocov author to make the tool a bit more robust. But I would very much like to see central CI and coverage reporting. 

On 19/07/2012, at 11:54, Mark Ramm <mark.ramm-christensen at canonical.com> wrote:

> On 07/18/2012 12:51 PM, Gustavo Niemeyer wrote:
>> Hey Clint,
>> 
>> On Wed, Jul 18, 2012 at 12:57 PM, Clint Byrum <clint at ubuntu.com> wrote:
>>> Are we tracking test coverage? Seems like having coverage watched
>>> regularly would prevent this from becoming a problem.
>> It'd be nice indeed to have something monitoring the whole code base
>> on a per-line basis, and rejecting changes that uncover a given line.
>> We're not there yet.
>> 
>> gustavo @ http://niemeyer.net
>> 
> Easier than that would be something that runs tests and records how many tests were run and if there were any failures on every commit (or merge).
> 
> But I also just saw this:
> 
> https://groups.google.com/forum/?fromgroups#!topic/golang-nuts/abujHqfUbvo
> 
> So it looks like coverage tracking is getting to be more feasible.
> 
> --Mark
> 
> 
> -- 
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev