183
edits
CodeCoverage/Firefly: Difference between revisions
Jump to navigation
Jump to search
→FAQs
ChrisHofmann (talk | contribs) |
Mnandigama (talk | contribs) (→FAQs) |
||
| Line 67: | Line 67: | ||
*I can present the findings from branch coverage to interested parties one on one. | *I can present the findings from branch coverage to interested parties one on one. | ||
*I do not have plans in place to implement a general availability of 'branch coverage' results in this Quarter. | *I do not have plans in place to implement a general availability of 'branch coverage' results in this Quarter. | ||
Q. What are the known limitations of line coverage data ? | |||
*If you have a multi conditional line like if(test)?dothis:dothat, even if both conditions are not tested, line coverage counts this line as covered. | |||
*If you have if(this&that||whatever) , the line would be shown as covered for testing one condition even if the rest are not covered. | |||
*Inlined functions may appear as not being covered. | |||
*But the '''important point''' is these discrepancies would generate a statistically insignificant variations in the coverage %. | |||
*When we pick up critical files we should not only pay attention to uncovered lines, but also to multi branch lines as well. | |||
Q. What is the format in which you are presenting the code coverage results analysis ? | Q. What is the format in which you are presenting the code coverage results analysis ? | ||