2013 IEEE Sixth International Conference on Software Testing, Verification and Validation 2013
DOI: 10.1109/icst.2013.21
|View full text |Cite
|
Sign up to set email alerts
|

Analysis and Prediction of Mandelbugs in an Industrial Software System

Abstract: Mandelbugs are faults that are triggered by complex conditions, such as interaction with hardware and other software, and timing or ordering of events. These faults are considerably difficult to detect with traditional testing techniques, since it can be challenging to control their complex triggering conditions in a testing environment. Therefore, it is necessary to adopt specific verification and/or fault-tolerance strategies for dealing with them in a cost-effective way. In this paper, we investigate how to… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
4
3
1

Relationship

2
6

Authors

Journals

citations
Cited by 26 publications
(8 citation statements)
references
References 29 publications
0
8
0
Order By: Relevance
“…Since software bugs are human mistakes in the source code, the traditional fault-tolerance strategies for hardware and network faults often do not apply. For example, if a service is broken because of a regression bug, then retrying to execute the service API with the same inputs would result again in a failure; a retrial would only succeed in the case that the software bug is triggered by a transient condition, such as a race condition [6,21,22]. If recovery is not possible, the failed operation must be necessarily aborted and the user should be notified [43,47], so that the failure can be handled at a higher level of the business logic.…”
Section: Overview On the Research Problemmentioning
confidence: 99%
“…Since software bugs are human mistakes in the source code, the traditional fault-tolerance strategies for hardware and network faults often do not apply. For example, if a service is broken because of a regression bug, then retrying to execute the service API with the same inputs would result again in a failure; a retrial would only succeed in the case that the software bug is triggered by a transient condition, such as a race condition [6,21,22]. If recovery is not possible, the failed operation must be necessarily aborted and the user should be notified [43,47], so that the failure can be handled at a higher level of the business logic.…”
Section: Overview On the Research Problemmentioning
confidence: 99%
“…Although the testing phase is not the final one, and more bugs of this type are expected to surface in later stages, our conjecture is confirmed by the high percentage of not tried or not available cases. Considering their high impact at operational time , this aspect should be improved. On single CSCIs, we observed again no significant correlation amongst the proportion of not always reproducible defects and any of the testing metrics.…”
Section: Resultsmentioning
confidence: 99%
“…ML algorithms show promising performance in solving SFP problem. Several algorithms are used such as Naive Bayes (NB) [12], Multilayer Perceptron (MLP) [13], Case-based Reasoning (CR) [14], Artificial Neural Networks [15], Deep learning methods [1], Support Vector Machine (SVM) [16], Bayesian Networks (BN) [17], Decision Trees (DT) [18], Multinomial Logistic Regression (MLR) [13] and Logistic Regression (LR) [17]. Several public bechmarck datasets are available online, and researchers employed their proposed algorithms and compare the obtained results with the literature.…”
Section: A Software Fault Predictionmentioning
confidence: 99%
“…The authors applied SVM and NB machine learning algorithms, and NB results outperform SVM. Carrozza et al [13] examine five ML algorithms (i.e., MLR, BN, NB, SVM, abd DT) over several datasets from NASA repository. The performance of MLP and SVM outperform other algorithms.…”
Section: A Software Fault Predictionmentioning
confidence: 99%