Home > Research > Publications & Outputs > No PAIN, No Gain? The utility of parallel fault...

Links

Text available via DOI:

View graph of relations

No PAIN, No Gain? The utility of parallel fault injections

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSNConference contribution/Paperpeer-review

Published

Standard

No PAIN, No Gain? The utility of parallel fault injections. / Winter, S.; Schwahn, O.; Natella, R.; Suri, Neeraj; Cotroneo, D.; J., Knoop (Editor); U., Zdun (Editor).

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering. IEEE, 2015. p. 494-505.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSNConference contribution/Paperpeer-review

Harvard

Winter, S, Schwahn, O, Natella, R, Suri, N, Cotroneo, D, J., K (ed.) & U., Z (ed.) 2015, No PAIN, No Gain? The utility of parallel fault injections. in 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering. IEEE, pp. 494-505. https://doi.org/10.1109/ICSE.2015.67

APA

Winter, S., Schwahn, O., Natella, R., Suri, N., Cotroneo, D., J., K. (Ed.), & U., Z. (Ed.) (2015). No PAIN, No Gain? The utility of parallel fault injections. In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering (pp. 494-505). IEEE. https://doi.org/10.1109/ICSE.2015.67

Vancouver

Winter S, Schwahn O, Natella R, Suri N, Cotroneo D, J. K, (ed.) et al. No PAIN, No Gain? The utility of parallel fault injections. In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering. IEEE. 2015. p. 494-505 https://doi.org/10.1109/ICSE.2015.67

Author

Winter, S. ; Schwahn, O. ; Natella, R. ; Suri, Neeraj ; Cotroneo, D. ; J., Knoop (Editor) ; U., Zdun (Editor). / No PAIN, No Gain? The utility of parallel fault injections. 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering. IEEE, 2015. pp. 494-505

Bibtex

@inproceedings{ba6fda3b691943cab118fa8e06fb56c6,
title = "No PAIN, No Gain? The utility of parallel fault injections",
abstract = "Software Fault Injection (SFI) is an establishedtechnique for assessing the robustness of a software under test byexposing it to faults in its operational environment. Depending onthe complexity of this operational environment, the complexityof the software under test, and the number and type of faults,a thorough SFI assessment can entail (a) numerous experimentsand (b) long experiment run times, which both contribute to aconsiderable execution time for the tests.In order to counteract this increase when dealing with complexsystems, recent works propose to exploit parallel hardware toexecute multiple experiments at the same time. While PArallelfault INjections (PAIN) yield higher experiment throughput,they are based on an implicit assumption of non-interferenceamong the simultaneously executing experiments. In this paperwe investigate the validity of this assumption and determinethe trade-off between increased throughput and the accuracyof experimental results obtained from PAIN experiments",
keywords = "Robustness testing, Software fault injection, Test interference, Software engineering, Fault injection, Software fault, Software testing",
author = "S. Winter and O. Schwahn and R. Natella and Neeraj Suri and D. Cotroneo and Knoop J. and Zdun U.",
year = "2015",
month = may,
day = "16",
doi = "10.1109/ICSE.2015.67",
language = "English",
isbn = "9781479919345",
pages = "494--505",
booktitle = "2015 IEEE/ACM 37th IEEE International Conference on Software Engineering",
publisher = "IEEE",

}

RIS

TY - GEN

T1 - No PAIN, No Gain? The utility of parallel fault injections

AU - Winter, S.

AU - Schwahn, O.

AU - Natella, R.

AU - Suri, Neeraj

AU - Cotroneo, D.

A2 - J., Knoop

A2 - U., Zdun

PY - 2015/5/16

Y1 - 2015/5/16

N2 - Software Fault Injection (SFI) is an establishedtechnique for assessing the robustness of a software under test byexposing it to faults in its operational environment. Depending onthe complexity of this operational environment, the complexityof the software under test, and the number and type of faults,a thorough SFI assessment can entail (a) numerous experimentsand (b) long experiment run times, which both contribute to aconsiderable execution time for the tests.In order to counteract this increase when dealing with complexsystems, recent works propose to exploit parallel hardware toexecute multiple experiments at the same time. While PArallelfault INjections (PAIN) yield higher experiment throughput,they are based on an implicit assumption of non-interferenceamong the simultaneously executing experiments. In this paperwe investigate the validity of this assumption and determinethe trade-off between increased throughput and the accuracyof experimental results obtained from PAIN experiments

AB - Software Fault Injection (SFI) is an establishedtechnique for assessing the robustness of a software under test byexposing it to faults in its operational environment. Depending onthe complexity of this operational environment, the complexityof the software under test, and the number and type of faults,a thorough SFI assessment can entail (a) numerous experimentsand (b) long experiment run times, which both contribute to aconsiderable execution time for the tests.In order to counteract this increase when dealing with complexsystems, recent works propose to exploit parallel hardware toexecute multiple experiments at the same time. While PArallelfault INjections (PAIN) yield higher experiment throughput,they are based on an implicit assumption of non-interferenceamong the simultaneously executing experiments. In this paperwe investigate the validity of this assumption and determinethe trade-off between increased throughput and the accuracyof experimental results obtained from PAIN experiments

KW - Robustness testing

KW - Software fault injection

KW - Test interference

KW - Software engineering

KW - Fault injection

KW - Software fault

KW - Software testing

U2 - 10.1109/ICSE.2015.67

DO - 10.1109/ICSE.2015.67

M3 - Conference contribution/Paper

SN - 9781479919345

SP - 494

EP - 505

BT - 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

PB - IEEE

ER -