Friday, February 13, 2009
NetObjectives (a focus on lean development)
NetObjectives are creating some great content. I listen to the podcast. Take some time to browse their resources.
Visual Studio... can look like TextMate
At home I'm a mac user. I love my mac (although it could stand to run faster)..
Rob Conery did an ace job of styling Visual Studio to look like TextMate.
Now less electrons need to die each second with your new black background. :)
Joking aside.. looking at a screen all day is like looking at a lightbulb. It is best if you can keep things dark but clear.
Rob Conery did an ace job of styling Visual Studio to look like TextMate.
Now less electrons need to die each second with your new black background. :)
Joking aside.. looking at a screen all day is like looking at a lightbulb. It is best if you can keep things dark but clear.
Coverage doesn't mean anything...
... is like saying "Wii-Fit doesn't make you fit, because you can just step on and off and the game thinks you are exercising".
If you do this, you are just fooling yourself.
Coverage means nothing unless you assume you are working in an environment where developers are writing good unit test. With this assumption, suddenly it becomes a great measure of how much of the code is untested! [or in BDD lingo.. how much of your code is not required to satisfy the current set of automated requirements indicating either a requirements gap or too much code!]
If you do this, you are just fooling yourself.
Coverage means nothing unless you assume you are working in an environment where developers are writing good unit test. With this assumption, suddenly it becomes a great measure of how much of the code is untested! [or in BDD lingo.. how much of your code is not required to satisfy the current set of automated requirements indicating either a requirements gap or too much code!]
100% Coverage
To my mind 100% coverage should mean all the code we as a team have chosen to test is tested.
If you decide 'generated code doesn't need tests.. as long as the generator is tested and an example is tested' .. then I say you are still 100%
If you decide 'getters and setters don't need testing' that's fine... exclude them from your coverage.
If you explicitly exclude something from your coverage statistics, then tell your tool. In NCover.. you can put attributes on the things you want to exclude.
Do that and you can get to 100%.
I'll leave the decision as to what things should be tested to the reader... for now.
If you decide 'generated code doesn't need tests.. as long as the generator is tested and an example is tested' .. then I say you are still 100%
If you decide 'getters and setters don't need testing' that's fine... exclude them from your coverage.
If you explicitly exclude something from your coverage statistics, then tell your tool. In NCover.. you can put attributes on the things you want to exclude.
Do that and you can get to 100%.
I'll leave the decision as to what things should be tested to the reader... for now.
Subscribe to:
Posts (Atom)