Prioritization of Test Cases in MUMCUT Test Sets: An Empirical Study

Yu, Yuen-Tak; Lau, Man Fai

doi:10.1007/3-540-48046-3_19

Cited by 4 publications

(8 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Based on these considerations, we shall analyze fault classes that are described as follows. Our fault classes are similar to those hypothesized in Chen and Lau [2001], Chen et al [1999], Foster [1984], Kuhn [1999], Paradkar et al [1997], Tai [1996], Tai and Su [1987], Tsuchiya and Kikuno [2002], Weyuker et al [1994], Yu and Lau [2002], and Yu et al [2003], as will be reviewed in Section 2.4.…”

Section: Definition Of Fault Classesmentioning

confidence: 57%

“…It follows that BASIC guarantees to detect not only its target fault LNF, but also TOF and LOF. From Figure 5, it is not surprising that BASIC detects all the classes of faults higher up in the hierarchy (TNF, ORF, and ENF) as well, but as noted earlier by Lau 1997, 2001;Chen et al 1999;Yu and Lau 2002], it may not be able to detect the stronger classes of faults (that is, LIF and LRF).…”

Section: The Modified Condition/decision Coverage (Mc/dc) Criterionmentioning

confidence: 87%

“…It uses a modified Statechart notation in which the conditions for state transitions are represented in the form of AND/OR tables, which are simply a readable version of Boolean expressions in DNF (see Table II for a sample). Experiments have been reported that used different strategies to generate test cases from Boolean expressions in the specification of an aircraft collision avoidance system called TCAS II [Kobayashi et al 2002;Tai 1996;Weyuker et al 1994;Yu and Lau 2002;Yu et al 2003]. …”

Section: Boolean Expressions and Fault Classes In Software Systemsmentioning

confidence: 99%

See 2 more Smart Citations

An extended fault class hierarchy for specification-based testing

Lau

2005

ACM Trans. Softw. Eng. Methodol.

Self Cite

122

View full text Add to dashboard Cite

Kuhn, followed by Tsuchiya and Kikuno, have developed a hierarchy of relationships among several common types of faults (such as variable and expression faults) for specification-based testing by studying the corresponding fault detection conditions. Their analytical results can help explain the relative effectiveness of various fault-based testing techniques previously proposed in the literature. This article extends and complements their studies by analyzing the relationships between variable and literal faults, and among literal, operator, term, and expression faults. Our analysis is more comprehensive and produces a richer set of findings that interpret previous empirical results, can be applied to the design and evaluation of test methods, and inform the way that test cases should be prioritized for earlier detection of faults. Although this work originated from the detection of faults related to specifications, our results are equally applicable to program-based predicate testing that involves logic expressions.

show abstract

Section: Definition Of Fault Classesmentioning

confidence: 57%

Section: The Modified Condition/decision Coverage (Mc/dc) Criterionmentioning

confidence: 87%

Section: Boolean Expressions and Fault Classes In Software Systemsmentioning

confidence: 99%

See 1 more Smart Citation

An extended fault class hierarchy for specification-based testing

Lau

2005

ACM Trans. Softw. Eng. Methodol.

Self Cite

122

View full text Add to dashboard Cite

show abstract

“…[2,11,12,20,[22][23][24][25][26][27][28][29][30][31][32][33][34][35][36] MCF IDNF A fault where the specification contains one or more conditions not implemented by the programmer (e.g. bc + be + def ) [2,3,11,12,[19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35][36]64] A literal in an expression is omitted. It also known as LOF.…”

Section: Gfmentioning

confidence: 99%

“…S D = abc + be + def for IDNF; S G = abc(de + f + h + ei)ḡ for GF) ReferenceReplace one occurrence of a variable by its negation (e.g.ābc + be + def )[2,11,12,[19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35][36] Occur when an atomic Boolean literal, say a, is replaced by its negation. It is also called Literal Negation Fault (LNF).GFReplace an occurrence of a variable/condition/clause by its negation in the formula.…”

mentioning

confidence: 99%

Redefinition of Fault Classes in Logic Expressions

Paul

Lau

2012

2012 12th International Conference on Quality Software

View full text Add to dashboard Cite

Fault-based testing selects test cases to detect hypothesized faults. In logic expression testing, many fault classes have been defined by researchers based on the syntax of the expressions. Due to the syntactic nature of the logic expressions, some fault classes may exist in one form (say, disjunctive normal form -DNF) of the logic expressions but not in other forms (say, general form). As a result, different faultbased testing techniques have been developed for different types of logic expressions and these techniques have different fault detecting capabilities. For example, some have high detecting power in DNF but low detecting power in the general form. Another complication arises when software developers decide which forms of logic expressions should be used in the first place. Should software developers use the general form for flexibility but compromise that with fewer fault classes and less fault detection? Or should they use DNF for more fault classes and, hence, better fault detection (because software developers have more "hypothesized faulty" scenarios to test) but sacrificing the generality of the expressions. In this paper, we propose a set of uniform definitions of fault classes such that they can be applied irrespective of the syntactic nature of the logic expressions, to produce consistent fault-based testing techniques and fault detection capabilities.

show abstract

Fault-based test suite prioritization for specification-based testing

Lau

2012

Information and Software Technology

View full text Add to dashboard Cite

Prioritization of Test Cases in MUMCUT Test Sets: An Empirical Study

Cited by 4 publications

References 13 publications

An extended fault class hierarchy for specification-based testing

An extended fault class hierarchy for specification-based testing

Redefinition of Fault Classes in Logic Expressions

Fault-based test suite prioritization for specification-based testing

Contact Info

Product

Resources

About