• Corpus ID: 13818014

Structuring Software Fault Injection Tools for Programmatic Evaluation

@inproceedings{Pirl2017StructuringSF,
  title={Structuring Software Fault Injection Tools for Programmatic Evaluation},
  author={Lukas Pirl and Lena Feinbube and Andreas Polze},
  year={2017}
}
The increasing complexity of software systems challenges the assurance of the likewise increasing dependability demands. Software fault injection is a widely accepted means of assessing dependability, but far less accessible and integrated into engineering practices than unit or integration testing. To address this issue, we present a dataset of existing fault injection tools in a programmatically evaluable model. Our Fault Injection ADvisor (FIAD) suggests applicable fault injectors mainly by… 
thinkmind.org

Figures from this paper

References

SHOWING 1-10 OF 23 REFERENCES

A Generic Fault Model for Quality Assurance

This paper challenges the idea of using coverage criteria for test selection and instead proposes an approach based on fault models that instantiate the developed general fault model to describe existing fault models and shows by example how to derive test cases.

Assessing Dependability with Software Fault Injection

This survey provides a comprehensive overview of the state of the art on Software Fault Injection to support researchers and practitioners in the selection of the approach that best fits their dependability assessment goals.

Fault Injection Experiments Using FIAT

FIAT is capable of emulating a variety of distributed system architectures and it provides the capabilities to monitor system behavior and inject faults for the purpose of experimental characterization and validation of a system's dependability.

A Survey on Fault Injection Techniques

A survey on fault injection techniques with comparison of the different injection techniques and an overview on the different tools is presented.

Dependability Benchmarking: making choices in an n-dimensional problem space

The definition of all the dimensions of the problem and the agreement of the community on a basic set of components that constitute a possible framework for dependability benchmarking seem to us a first step in the proposal of actual dependability benchmarks.

Why Do Computers Stop and What Can Be Done About It?

  • J. Gray
  • Computer Science
    Symposium on Reliability in Distributed Software and Database Systems
  • 1986
It is pointed out that faults in production software are often soft (transient) and that a ransaction mechanism combined with persistent processpairs provides fault-tolerant execution -- the key to software fault -tolerance.

Software testing: a research travelogue (2000–2014)

The goal of this paper is to provide an accounting of some of the most successful research performed in software testing since the year 2000, and to present what appear to be the most significant challenges and opportunities in this area.

Why Do Internet Services Fail, and What Can Be Done About It?

It is found that operator errors are their primary cause, operator error is the most difficult type of failure to mask, service front-ends are responsible for more problems than service back-ends but fewer minutes of unavailability, and that online testing and more thoroughly exposing and detecting component failures could reduce system failure rates for at least one service.

Software For Dependable Systems Sufficient Evidence

This software for dependable systems sufficient evidence helps people to enjoy a good book with a cup of coffee in the afternoon, instead they juggled with some malicious bugs inside their desktop computer.

The Antifragile Organization

Failure is inevitable. Disks fail. Software bugs lie dormant waiting for just the right conditions to bite. People make mistakes. Data centers are built on farms of unreliable commodity hardware. If…