Proceedings of International Workshop on Engineering Simulations for Cyber-Physical Systems 2013
DOI: 10.1145/2589650.2559629
|View full text |Cite
|
Sign up to set email alerts
|

Combining Fault-Injection with Property-Based Testing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
5
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
3
1

Relationship

2
2

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 17 publications
0
5
0
Order By: Relevance
“…The CopterSim library can either be used from a Graphical User Interface (GUI) to manually add and move copters, or from a program that auto-generates tests and injects faults. All fault injection is done with probes from the FaultCheck tool [10], linked to the simulator.…”
Section: Simulation and Fault Injectionmentioning
confidence: 99%
See 2 more Smart Citations
“…The CopterSim library can either be used from a Graphical User Interface (GUI) to manually add and move copters, or from a program that auto-generates tests and injects faults. All fault injection is done with probes from the FaultCheck tool [10], linked to the simulator.…”
Section: Simulation and Fault Injectionmentioning
confidence: 99%
“…This way, we could randomly generate pilot control commands and inject faults during thousands of automatically generated simulations to see when a collision occurs. For fault injection, we used the FaultCheck tool [10] and for generating tests we used the Erlang QuickCheck tool [11]. When we had a sequence of pilot and fault injection commands that led to a collision, we used the shrinking feature of QuickCheck to get a shorter test sequence of commands that leads to a collision.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…FI can e.g. be carried out early in the development process for models of hardware [2]- [4], models of software [5]- [8], source code [9], [10], and at later stages of the development process, for software deployed on target hardware [11]- [16]. When working with FI, it is common to manually create input stimuli for a System Under Test (SUT) and run it without faults, and save the state of the SUT during this run as the golden run.…”
Section: Introductionmentioning
confidence: 99%
“…When doing PBT, inputs are automatically generated and a model of the software is used to evaluate whether it fulfils its specification, whereby the golden run is generated automatically for each test sequence based on the model. Previously, we have introduced the concept of combining techniques from the areas of PBT and FI using the commercially available PBT-tool QuickCheck [18] and our FI-tool FaultCheck to test functional and non-functional requirements simultaneously [10]. By using techniques from PBT while doing FI, we can automatically generate golden runs during our experiments and test the SUT using thousands of input sequences and fault combinations.…”
Section: Introductionmentioning
confidence: 99%