James Whittaker is the author of books like How To Break Software. He ran one of the few university-level testing programs at Florida Tech. He's now as Microsoft and helping Visual Studio become better at testing. The guys at .Net Rocks caught up with him for an interview. James explains what he thinks the future of testing is and what's right and wrong with testing at Microsoft. Put this on your Zune/iPod. It's worth the hour.
PingBack from http://www.alvinashcraft.com/2009/01/10/dew-drop-january-10-2009/
ReplyDelete"...if all developers can understand that you can have 100% code coverage and you can still have lots and lots of bug..."
ReplyDelete1. Nobody would use the term "100% code coverage". It means as much as "100 foos". When you talk about code coverage and attach a percentage in front of it, you better mention what code coverage criteria you are using. It's hard to imagine such thing as 100% code coverage that's useful, at least not in real product.
2. Code coverage doesn't mean code quality. Code with higher % code code coverage (any criteria) does not mean better quality.
"...if all developers can understand that you can have 100% code coverage and you can still have lots and lots of bug..."
ReplyDelete1. Nobody would use the term "100% code coverage". It means as much as "100 foos". When you talk about code coverage and attach a percentage in front of it, you better mention what code coverage criteria you are using. It's hard to imagine such thing as 100% code coverage that's useful, at least not in real product.
2. Code coverage doesn't mean code quality. Code with higher % code code coverage (any criteria) does not mean better quality.