Fault Injection Experiments Using FIAT
IEEE Transactions on Computers
Theoretical Computer Science
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
An approach towards benchmarking of fault-tolerant commercial systems
FTCS '96 Proceedings of the The Twenty-Sixth Annual International Symposium on Fault-Tolerant Computing (FTCS '96)
Automated Robustness Testing of Off-the-Shelf Software Components
FTCS '98 Proceedings of the The Twenty-Eighth Annual International Symposium on Fault-Tolerant Computing
A framework and a tool for robustness testing of communicating software
Proceedings of the 2007 ACM symposium on Applied computing
A model-based approach for robustness testing
TestCom'05 Proceedings of the 17th IFIP TC6/WG 6.1 international conference on Testing of Communicating Systems
Hi-index | 0.00 |
In this paper, we suggest a methodology for testing robustness of Real-Time Component-Based Systems (RTCBS). A RTCBS system is described as a collection of components where each component is modeled as a Timed Input-Output Automaton (TIOA). For each component, we handle two specifications: a nominal one and a degraded one. We extract test sequences from the nominal specification and we inject automatically faults in order to model hostile environments. Then we present an adequate test architecture consisting of the System Under Test (SUT) of components, and a distributed tester that consists of a set of coordinating testers. Each tester is dedicated to test a single SUT component. A test execution algorithm is presented. Testing the SUT is divided into two phases. In the first phase, the tester executes the generated test sequences of each component in isolation and records the feedback of this experimentation. The robustness is checked by verifying if the recorded results are accepted by the degraded specification of each component. If all components are robust according to the inserted hazards, we check the robustness of communications between components respecting the same process described before.