Modified condition/decision coverage: Difference between revisions

Revision as of 23:29, 12 August 2023

Revision as of 07:19, 1 November 2023

Line 62:

}

}

</syntaxhighlight>if the definition of a decision is treated as if it is ana boolean expression that changes the control flow of the program (the text in brackets in an 'if' statement) then one may think that Function B is likely to have higher MC/DC than Function A for a given set of test cases (easier to test because it needs less tests to achieve 100% MC/DC coverage), even though functionally both are the same.<ref>http://www.hbni.ac.in/phdthesis/engg/ENGG02201004005.pdf {{Bare URL PDF|date=March 2022}}</ref>

However, what is wrong in the previous statement is the definition of decision. A decision includes 'any' boolean expression, even for assignments to variables. In this case, the three assignments should be treated as a decision for MC/DC purposes and therefore the changed code needs exactly the same tests and number of tests to achieve MC/DC than the first one. Some code coverage tools do not use this strict interpretation of a decision and may produce false positives (reporting 100% code coverage when indeed this is not the case). {{Citation needed|date=November 2022}}