2016 IEEE Ninth International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2016
DOI: 10.1109/icstw.2016.44
|View full text |Cite
|
Sign up to set email alerts
|

Evaluating the Effectiveness of BEN in Localizing Different Types of Software Fault

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 9 publications
(3 citation statements)
references
References 20 publications
0
3
0
Order By: Relevance
“…In addition to framework and method, some PSSs present a tool as a major contribution. For example in [59], a tool named BEN is developed and evaluated on localising different types of software fault. Evaluation or comparison refers to the PSSs evaluating other methods or systems, i.e.…”
Section: Rq2 What Research Approaches (Research Facets) Have Been Fomentioning
confidence: 99%
“…In addition to framework and method, some PSSs present a tool as a major contribution. For example in [59], a tool named BEN is developed and evaluated on localising different types of software fault. Evaluation or comparison refers to the PSSs evaluating other methods or systems, i.e.…”
Section: Rq2 What Research Approaches (Research Facets) Have Been Fomentioning
confidence: 99%
“…For example, there exists three partitions with blocks [1,2], [1,2,3], [1,2] for three parameters. Supposing base choice block are '1', '3', '1', the base choice test is [1,3,1], and the following additional tests would be generated:…”
Section: Definition 9 Basic Choice Coverage (Bcc)mentioning
confidence: 99%
“…In recent years, how to use test suite and their testing results to diagnose the root cause of failures has attracted much attention [1,2,8,10]. Nie et al [10] proposed the minimum failure-causing schema, which also is called the minimal failureinducing mode, and highlighted the MFS to help locate and understand the bug(s) in source code [8].…”
Section: Introductionmentioning
confidence: 99%