Adding Clover to Automated Builds

Last week I filled out a purchase order for Clover after some evaluation of various unit testing code coverage tools. I went with Clover because $1500 for the server edition isn’t really that significant a cost even if the experiment doesn’t work out. So starting next week we’ll be running code coverage reports with our ongoing projects. I expect the feedback loop to be pretty helpful. I’ll be really happy at first if we can get 50% coverage at first on average.