Experimental evaluation of the variation in effectiveness for DC, FPC and MC/DC test criteria

Kapoor, Kalpesh; Bowen, Jonathan P.

doi:10.1109/isese.2003.1237977

Cited by 19 publications

(9 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The size of the test suite is also comparable to BOR. Reported [8] that average effectiveness of MC/DC remains constant even with increase in number of conditions. MI and MUMCUT does not any restriction on number of variable and number of occurrences of the variables It has been shown [35] that MUMCUT detects all faults detected by MI and the test generated is a subset of test sets generated by MI and the size of test suit is much smaller.…”

Section: Discussionmentioning

confidence: 99%

Fault Based Techniques For Testing Boolean Expressions: A Survey

Badhera¹

2012

IJCSES

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Fault Based Techniques For Testing Boolean Expressions: A Survey

Badhera¹

2012

IJCSES

View full text Add to dashboard Cite

show abstract

“…Boolean expressions from literature ranging from 3 variables to 12 variables used for assessing the, performance and effectiveness of the various testing techniques based on mutation analysis. Mutants were generated for operator fault (ORF,ENF,VNF,ASF) and operand fault (MVF,VRF,CCF,CDF,SA0,SA1 [8] that average effectiveness of MC/DC remains constant even with increase in number of conditions. One approach to overcome the weakness of these is to combine these techniques.…”

Section: Discussionmentioning

confidence: 99%

“…Empirical evaluation of testing technique for Boolean specifications were studied in [8,9,11,13] has explored the relationship between various fault types. It is shown that ENF are weakest faults in the sense that any technique which catches stronger faults are likely to find ENF's.…”

Section: Fault Classesmentioning

confidence: 99%

Boolean Specification Based Testing Techniques: A Survey

Badhera¹,

Taruna²

2012

Computer Science Conference Proceedings

View full text Add to dashboard Cite

show abstract

“…Another aspect for using structural code coverage metrics for the evaluation of the testing effort is the fact that the test set depends on the structure of the code, as shown in [20] In [21] different code coverage metrics (decision coverage, full predicate coverage, and MC/DC) are compared regarding their effectiveness in finding errors. One result of this work is that, in general, the MC/DC criterion was found to be effective [for detecting faults] independent of the number of conditions in the Boolean decision.…”

Section: ---T Ft --T Fft -T Ffftt}mentioning

confidence: 99%

Reasonability of MC/DC for safety-relevant software implemented in programming languages with short-circuit evaluation

Kandl

Chandrashekar²

2014

Computing

View full text Add to dashboard Cite

Modified condition/decision coverage (MC/DC) is a structural code coverage metric, originally defined in the standard DO-178B, intended to be an efficient coverage metric for the evaluation of the testing process of software incorporating decisions with complex Boolean expressions. The upcoming standard ISO 26262 for safety-relevant automotive systems prescribes MC/DC for ASIL D as a highly recommended coverage metric. One assumed benefit of MC/DC is that it requires a much smaller number of test cases in comparison to multiple condition coverage (MCC), while sustaining a quite high error-detection probability. Programming languages like C, commonly used for implementing software for the automotive domain, are using short-circuit evaluation. For short-circuit evaluation the number of test cases for MCC is much smaller than in a non-short-circuit environment because many redundant test cases occur. We evaluated the trade-off between the number of test cases for MCC and MC/DC for a case study from the automotive domain and observed a very low overhead (only 5 %) for the number of test cases necessary for MCC compared to MC/DC. This motivated an analysis of programs containing decisions where the number and structure of the referring Boolean expressions vary. Our results show that the overhead for a test suite for MCC is on the average only about 35 % compared to MC/DC and the maximum overhead is approximately 100 % (for decisions with up to 5 conditions). This means that a test set for MCC is in the worst case around twice as big as a test set for MC/DC for a program with short-circuit evaluation with maximum 5 conditions. Considering the lower error-detection effectiveness of MC/DC compared to MCC, we conclude with the strong recommendation to use MCC as a coverage metric for testing safety-relevant software (with a limited number of conditions) implemented in programming languages with short-circuit evaluation.

show abstract

Experimental evaluation of the variation in effectiveness for DC, FPC and MC/DC test criteria

Abstract: Abstract

Cited by 19 publications

References 34 publications

Fault Based Techniques For Testing Boolean Expressions: A Survey

Fault Based Techniques For Testing Boolean Expressions: A Survey

Boolean Specification Based Testing Techniques: A Survey

Reasonability of MC/DC for safety-relevant software implemented in programming languages with short-circuit evaluation

Contact Info

Product

Resources

About