Click here to Skip to main content
15,867,765 members

Survey Results

Do you measure code coverage?

Survey period: 27 Mar 2017 to 3 Apr 2017

Code Coverage: the degree to which the source code of a program is executed when a particular test suite runs.

OptionVotes% 
Yes - to ensure our unit tests cover all execution paths15116.00
Yes - to know how much of our code is actually run in production242.54
Yes - for both tests and in production434.56
Yes - for other reasons262.75
No - but we are planning to727.63
No - it's a pointless metric848.90
No - we don't have the tools or expertise14415.25
No - we don't have time11812.50
No28229.87



 
GeneralRe: No Pin
Rob Philpott28-Mar-17 2:31
Rob Philpott28-Mar-17 2:31 
PraiseRe: No Pin
den2k8828-Mar-17 4:44
professionalden2k8828-Mar-17 4:44 
GeneralRe: No Pin
Agent__00729-Mar-17 1:52
professionalAgent__00729-Mar-17 1:52 
GeneralYes i do, first option but! Pin
HobbyProggy26-Mar-17 19:26
professionalHobbyProggy26-Mar-17 19:26 
GeneralNo Pin
Nelek26-Mar-17 18:58
protectorNelek26-Mar-17 18:58 
GeneralI selected the first option but, Pin
dan!sh 26-Mar-17 18:08
professional dan!sh 26-Mar-17 18:08 
I do not believe that we can slap on a number to ensure that tests are actually meaningful. I have worked in places where we had to make sure that 80% or more coverage was required. Getting to that number, honestly, is very easy. Getting to that number with meaningful tests, may or may not be.

So, yes we should look at the coverage but no that does not tell how well we have unit tested the code.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[^]

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.