Outstanding! On Sun, Jun 26, 2016 at 3:13 AM, Tomaz Muraus <[email protected]> wrote:
> Nice :thumbsup: > > We used to run coverage.py and upload reports to Apache build servers, but > this hasn't been running for a while now and it was kinda pain to maintain > so I'm all for outsourcing it to a 3rd party service :) > > On Sun, Jun 26, 2016 at 11:58 AM, anthony shaw <[email protected]> > wrote: > > > Hi, > > > > As part of a goal to get more frequent releases, we have to keep our > > test coverage reasonably high and also make sure we don't merge > > untested code or unreachable/unmaintable code. > > > > The infra team have kindly enabled Coveralls.IO support and I've > > enabled this in TOX as part of our build. > > > > You can see now the reports - > > https://coveralls.io/github/apache/libcloud?branch=trunk when people > > raise pull requests it should add a comment to say whether the > > coverage has gone up or down. > > > > Coveralls has a neat interactive coverage viewer online, you can > > inspect code blocks covered for a build, its a lot easier than using > > coverage reports! > > > > We're at a healthy 90%- a great place to start from. It already > > uncovered an untested module, the storage driver for ninefold (who no > > longer exist!) > > > > Ant > > >
