Interesting idea here: applying automated quality checks just to a
*diff*, so you can use them as patch gating criteria *even if* you have
legacy code that doesn't pass them:
http://engineering.edx.org/2013/12/diff-cover-test-coverage-for-git-commits/
This could be particularly useful to us for improving our unit test
coverage - the integration tests run real servers, so collecting
coverage data is a bit of a pain, but unit tests run in the current process.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
Testing Solutions Team Lead