Here’s a few charts and such from the end of an iteration that the team I’m on just wrapped. I’d love to see any TFS charts of this nature or other solutions in JIRA, TeamCity, or whatever is used. Anyone else out there want to get a blog post up about it, I’ll add a link at the end of my entry here.
Lots of Tests, Good Continuous Integration Build
Gotta have solid test coverage for any reasonable expectation of maintenance. When I mean tests, I’m talking about properly abstracted, mocked, stubbed, faked, or otherwise built so as they don’t depend on all sorts of nonsensical external dependencies like file systems, database, or other things.
Code Coverage, in general keeps an upward trend!
100% is a little fanatical, but an upward trend after the beginning of a project and the initial work beginning is one of the best things to see. Code coverage with tests means you’ll be able to get all sorts of goodies: maintainable code, non-increasing tech debt, faster refactors, etc.
The Few Fixes Needed, Get Fixed Pretty Quick!
Unit test fixes. Should be quick, should be furiously done, and shouldn’t take more than about an hour on the infrequent times they occur at all.
Unit Test Coverage Up...
Increasing Count
…and of course, the burn down.
BURN baby BURN!
Burn Down
