Don't know if my first comment got through, so I'll try again. Did you try correlating a project's code coverage and the amount of open issues?
Branch Coverage is more important than Statement coverage, while measuring the thoroughness of tests.
+1 I am curious to find out if you tried to correlate branch coverage (instead of statement) and the presence of defects if it would not result in stronger correlation, but I am guessing yes.Did you try that? Can you share your findings?
We did. We didn't find any correlation yet. But we are looking into that.
OK. Because that sounds like it might be interesting for clarifying some of the myths you mention in the first paragraph. Keep us posted if you make some discoveries there ;)
Yes, knowing how coverage relates to problems encountered by users would be great information to have.
We are working on this. We will publish the results as soon as we have concrete findings. So far we have neither definite positive nor definite negative results for that question.
How do you measure JS code coverage?
Your first paragraph mentions the controversy around code coverage, but it looks like your results and research don't attempt to address that core issue, e.g. whether code coverage actually leads to fewer errors in the resulting project.
Which system do you use for code reviews? Is it's Gerrit: How did you integrate the coverage metrics into Gerrit?
In some ways not unexpected that coverage is inversely correlated to language type strength
Am confused with the below statement in future work section. the code that is being hit by the tests need to be instrumented. why do we need to instrument the tests?"In particular, the individual tools we use to measure coverage are not perfect. Large integration tests, end to end tests and UI tests are difficult to instrument, so large parts of code exercised by such tests can be misreported as non-covered. "
Apart from unit and integration testing are you also capturing statement coverage through manual functional test? What toolset you use for Java.
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.