Fault-Oriented Test Generation for Multicast Routing Protocol Design

Estrin, Deborah; Gupta, Sandeep

doi:10.1007/978-0-387-35394-4_6

Cited by 16 publications

(4 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is the case for instance in the so-called Fotg approach [11] (Fault Oriented Test Generation): starting from a fault introduced in a protocol specification (like a message loss, or a node crash), it consists in looking (forward) for an error state (a state in which a protocol fails to meet its requirement), and then to search (backward) for a test sequence leading from the initial state to this error state. Even if this approach seems well adapted to fault-tolerant protocols it only deals with single faults (one at a time), and uses a rather simple specification formalism (Finite State Machines).…”

Section: Introductionmentioning

confidence: 99%

A Model-Based Approach for Robustness Testing

Fernandez

Mounier

Pachon

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Robustness testing is a part of the validation process which consists in testing the behavior of a system implementation under exceptional execution conditions in order to check if it still fulfills some robustness requirements. We propose a theoretical framework for modelbased robustness testing together with an implementation within the If validation environment. Robustness test cases are generated from both a (partial) operational specification and an abstract fault model. This generation technique is inspired from the ones used in (classical) conformance testing -already implemented in several tools. This framework is illustrated on a small example.

show abstract

Section: Introductionmentioning

confidence: 99%

A Model-Based Approach for Robustness Testing

Fernandez

Mounier

Pachon

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Robustness testing is a necessary step to complement functional testing, and its role is to guarantee that the software behaviour is acceptable in the presence of internal or external failures, or stressful environmental conditions. In several robustness testing approaches, mostly based on conformance testing [13,16,18], the model used for representing the nominal behaviour is extended to allow the representation of behaviour in the presence of faults. A major limitation associated with such approaches is the fact that the fault model is reduced to that can be represented in the model, and also, that can be applied by a tester.…”

Section: Robustness Testingmentioning

confidence: 99%

Architectural-Based Validation of Fault-Tolerant Software

Brito

Lemos

Martins

et al. 2009

2009 Fourth Latin-American Symposium on Dependable Computing

View full text Add to dashboard Cite

Many architecture-centred approaches have been proposed for constructing dependable component-based systems. However, few of them provide an integrated solution for their development that combines fault prevention, fault removal, and fault tolerance techniques. This paper proposes a rigorous development approach based on an architectural abstraction, which combines formal methods and robustness testing. The architectural abstraction assumes a crash failure semantics, and when it is instantiated as an architectural element provides the basis for architecting fault tolerant systems. The architecture is formally specified using the B-Method and CSP. Assurances that the software system is indeed dependable are obtained by combining formal specification for removing ambiguities from the architectural representation, and robustness testing for validating the source code against its software architecture. The feasibility of the proposed approach is illustrated in the context of a financial critical system.

show abstract

“…Most importantly, the seminal work of David Lee and others [1], [15], [23], [24] illustrates the power of formal models in testing. Many authors have subsequently developed models for test case generation, verification, or model-checking of network protocols [3], [5], [7], [17], [29], [19].…”

Section: Introductionmentioning

confidence: 99%

Testing a Network by Inferring Representative State Machines from Network Traces

Griffeth¹,

Cantor²,

Djouvas³

2006

2006 International Conference on Software Engineering Advances (ICSEA'06)

View full text Add to dashboard Cite

Abstract-This paper describes an innovative approach to network testing based on automatically generating and analyzing state machine models of network behavior. The models are generated by the network test tool AGATE (Automatic Generator of Automata for TEsting), which is also described in this paper. The proposed test approach mimics experimental method, requiring repeated cycles of observing the network, modeling the network, making predictions about network behavior, and evaluating predictions. This paper focusses on the modeling step, in which the test tool AGATE automatically generates representative state machines from observed network traces. The generated state machines closely approximate the behavior of components of the network under test. Faults in the system may be immediately apparent from the state machines, but more importantly the state machines can be used for formal analysis. We propose this as a cost-effective alternative to manually defining a state machine before beginning tests.

show abstract

Fault-Oriented Test Generation for Multicast Routing Protocol Design

Cited by 16 publications

References 9 publications

A Model-Based Approach for Robustness Testing

A Model-Based Approach for Robustness Testing

Architectural-Based Validation of Fault-Tolerant Software

Testing a Network by Inferring Representative State Machines from Network Traces

Contact Info

Product

Resources

About