Released Sunday, November 23rd, 2014.
The holy practice of measuring code coverage:
- Without code coverage, how do you know if you are writing enough tests?
- Test First vs. Test Driven vs. Unit Testing
- The Wall of Shame
- Implementing a rule requiring a certain percentage of test coverage for a code base.
- Suppose I’m an “Application Development Manager” (yes there are people with that job, it is a real job) and I have teams that have different views / practices about testing, what’s wrong with having a baseline level of testing that I would mandate to promote software assurance as part of my job as the ADM is managing risk on behalf of the business in the software they are investing in.
- The MBA approach to code coverage
- Starting with a code coverage number can be helpful in some situations, but isn’t a good idea long term.
- Having confidence in your code
- Assuring quality code
- Is Code Coverage a Silver Bullet – http://www.stickyminds.com/article/code-coverage-silver-bullet
- For the Holidays – I’m going recommend fun agile games that will help your team improve – let’s start with – “Protection Poker” by Laurie Williams – http://collaboration.csc.ncsu.edu/laurie/Security/ProtectionPoker/
- Google, “Go to the Gemba” and read