Posts Tagged MC/DC


If the topic is software coverage (or code coverage): Please make sure that you and your counterpart understand the same measure by the same term.

If you use a tool to determine software coverage: Please check how the tool handles the two cases of doubt given in misapprehension 4.

Please keep an eye on the effort you need to reach e.g. 100% MC/DC: Is it in the right relation to the gain in relevance? Sometimes it may be better to spend this effort for other test activities!

Beware of fool’s gold: Don’t relax because you have reached 100%!

, , ,

No Comments

Misapprehension 6: Clever programming makes live easy

This seems to be a consequence from the misapprehension above. Unfortunately this is not correct.

Are two test cases sufficient for 100% MC/DC?

Because a clever programmer has extracted the combination of the conditions from the decision of the if-instruction, at a glance only two test cases seem to be necessary to reach 100% modified condition / decision coverage (MC/DC) for the software snippet on the left hand side in the figure above: One test case in which decision evaluates to true and one test case in which decision evaluates to false. However, the right hand side of the figure above reveals that Tessy has recognized the combination of the conditions in the assignment and therefore three test cases are necessary to reach 100% MC/DC. This prevents creative programming to by-pass correct determination of condition coverage.

, , , , ,

No Comments