MM-ulator: Towards a Common Evaluation Platform for Mixed Mode Environments
SIMPAR '08 Proceedings of the 1st International Conference on Simulation, Modeling, and Programming for Autonomous Robots
Execution path profiling for OS device drivers: viability and methodology
ISAS'08 Proceedings of the 5th international conference on Service availability
An extensible technique for high-precision testing of recovery code
USENIXATC'10 Proceedings of the 2010 USENIX conference on USENIX annual technical conference
The impact of fault models on software robustness evaluations
Proceedings of the 33rd International Conference on Software Engineering
A case study on state-based robustness testing of an operating system for the avionic domain
SAFECOMP'11 Proceedings of the 30th international conference on Computer safety, reliability, and security
Efficient Testing of Recovery Code Using Fault Injection
ACM Transactions on Computer Systems (TOCS)
A systematic review of software robustness
Information and Software Technology
| Hi-index | 0.00 |
Traditionally, in fault injection-based robustness evaluation of software (specifically for Operating Systems - OS's), faults or errors are injected at specific code locations. This paper studies the sensitivity and accuracy of the robustness evaluation results arising from varying the timing of injecting the faults into the OS. A strategy to guide the triggering of fault injection is proposed, based on the observation that the operational usage profile of a driver shows a high degree of regularity in the calls being made. The concept of call blocks (i.e., a distinct sequence of calls made to the driver) can be used to guide injections into different system states, corresponding to the driver operations carried out. A real-world case study compares the effectiveness of the proposed strategy to traditional location-based approaches, demonstrating that significant and useful insights can be gained by modulating the injection instants.