In the services team, we found that prominent coverage metrics are a very powerful motivator for keeping tests in order. We have set up 'voting' coverage reports, which fail the overall tests if coverage falls, and make it easy to check which lines aren't covered yet (via coveralls). In all repositories we enabled this for, test coverage has since stabilized around 80-90%.
Gabriel On Thu, Sep 3, 2015 at 4:31 PM, Steven Walling <[email protected]> wrote: > Just to hop on the bandwagon here: this seems like the only sane path going > forward. One unmentioned benefit is that this is a step toward continuous > deployment. Having integration tests run on every commit and then block > when there are failures is pretty much a requirement if Wikimedia ever > wants to get there. > > On Thu, Sep 3, 2015 at 1:43 PM Pine W <[email protected]> wrote: > > > I just want to say that I appreciate this overview. > > > > Pine > > _______________________________________________ > > Wikitech-l mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Gabriel Wicke Principal Engineer, Wikimedia Foundation _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
