Hardware Testing Using a Communication Protocol Conformance Testing Tool

Kahlouche, H.; Viho, César; Zendri, Massimo

doi:10.1007/3-540-49059-0_22

Cited by 7 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Among the case studies listed on the CADP web site, the tools are most frequently used for the formal specification and modeling of a system, which are then verified by model checking temporal logic properties and/or equivalence checking against a reference model (e.g., the expected service of a protocol). Some case studies additionally take advantage of more specific tools, e.g., for performance evaluation [18,3,11,7,9,14,45,55], (conformance) test generation [33,12,28,51,54,8,29,41,35,5], or generation of an executable prototype from the formal model [12,28,53,27,41,52,26].…”

Section: αFm: How Can the Approach Be Applied In Practice?mentioning

confidence: 99%

“…This approach permitted to detect 5 bugs." [33] The capability to generate counterexamples and witnesses, common to all enumerative techniques, is also judged an interesting asset. "Another important advantage of using CADP is that, when a property does not hold, the model checking algorithm generates a counter-example, i.e., an execution trace leading to a state in which the property is violated.…”

Section: Usefulness αFm: How Is Usefulness Achieved? Is the Approach ...mentioning

confidence: 99%

See 1 more Smart Citation

Is CADP an Applicable Formal Method?

Garavel¹,

Lang²,

Mateescu³

et al. 2021

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

show abstract

Section: αFm: How Can the Approach Be Applied In Practice?mentioning

confidence: 99%

Section: Usefulness αFm: How Is Usefulness Achieved? Is the Approach ...mentioning

confidence: 99%

Is CADP an Applicable Formal Method?

Garavel¹,

Lang²,

Mateescu³

et al. 2021

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

show abstract

“…Also a part of the TTCN test suite produced by ATM Forum has been checked with VTS (for soundness and laxity) [17] and some errors due to asynchronism were detected. Lotos: Several experiments [20], [21] consisted in using TGV on specifications of a multiprocessor architecture of Bull. Produced test cases have been executed by Bull on a simulator of the architecture.…”

Section: Case Studiesmentioning

confidence: 99%

TGV: theory, principles and algorithms

Jard

Jéron

2004

Int J Softw Tools Technol Transfer

256

160

View full text Add to dashboard Cite

This paper presents the TGV tool allowing the automatic synthesis of conformance test cases from a formal specification of a reactive system. TGV has been developped by Irisa Rennes and Verimag Grenoble, with the support of the Vasy team of Inria Rhônes-Alpes. The paper describes the main elements of the underlying testing theory, based on a model of transitions system which distinguishes inputs, outputs and internal actions, and based on the concept of conformance relation. The principles of the test synthesis process are explained as well as the main algorithms. We then describe the main characteristics of the TGV tool. As a conclusion, we describe some on going works in test synthesis. I. CONFORMANCE TESTINGTesting, in all its variations, is one of the most used validation techniques. In this paper, we focus on conformance testing applied to reactive systems. By reactive system, we mean a software component which reacts to stimuli of its environment. Conformance testing consists in checking that the behavior of a real implementation of a reactive system (IUT for Implementation Under Test) is correct with respect to a specification. The code of the IUT is unknown, and its behavior is only visible by interaction with a tester which controls and observes the IUT through dedicated interfaces (called PCO for Points of Control and Observation). Conformance testing is a type of functional testing of a black box nature. A. Some basic conceptsIn the context of telecommunication protocols, the main concepts of this activity are described in the standard ISO 9646 [1]. Some of them are introduced here.A test case is an elementary test targeted to testing a particular functionality, called test purpose. A test suite is a set of test cases. The basic elements of a test case are interactions through PCO: outputs are stimuli sent in order to control the IUT's input events, inputs are observations of the IUT's output events. Inputs may lead to different verdicts. A Fail verdict denotes a divergence with the expected behaviour and the IUT is rejected. A Pass verdict is returned if the observation is correct and the test purpose is reached. An Inconclusive verdict is returned if a correct behavior is observed, but it is impossible to reach the test purpose. This is due to the fact that, in general, reactive systems cannot be completely controlled by a tester: it may have several outputs to the same input. The tester, specialized hardware, software or human operator, executes test cases. But as test cases are often described with some abstraction level (they are called abstract test cases), they must be translated into executable test cases. B. Formalizing for automationConformance testing is a costly activity which takes an important part in the global cost of a software. For a long time, the scientific community tries to automate the process of deriving test cases. For conformance testing, the reference behaviour is described by the specification which determines the verdicts. Automation thus induces formalizing the ...

show abstract

“…and a sound underlying theory (Tretmans, 1996) suggest the application of such formal methods for black box testing in industrial projects. Existing case studies (Fernandez et al, 1997;Kahlouche et al, 1998Kahlouche et al, , 1999Laurencot and Salva, 2005;Philipps et al, 2003;Kovács et al, 2003), report on the application of formal testing techniques to different sized applications. Basically, they report on the application of a particular test generation technique to certain problems.…”

Section: Introductionmentioning

confidence: 99%

RANDOM VS. SCENARIO-BASED VS. FAULT-BASED TESTING - An Industrial Evaluation of Formal Black-Box Testing Methods

Weiglhofer

Wotawa

2008

Proceedings of the Third International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

Given a formal model of a system under test there are different strategies for deriving test cases from such a model systematically. These strategies are based on different underlying testing objectives and concepts. Obviously, their usage has impact on the generated test cases. In this paper we evaluate random, scenariobased and fault-based test case generation strategies in the context of an industrial application and assess the advantages and disadvantages of these three strategies. The derived test cases are evaluated in terms of coverage and in terms of the detected errors on a commercial and on an open source implementation of the Voice-Over-IP Session Initiation Protocol.

show abstract

Hardware Testing Using a Communication Protocol Conformance Testing Tool

Cited by 7 publications

References 7 publications

Is CADP an Applicable Formal Method?

Is CADP an Applicable Formal Method?

TGV: theory, principles and algorithms

RANDOM VS. SCENARIO-BASED VS. FAULT-BASED TESTING - An Industrial Evaluation of Formal Black-Box Testing Methods

Contact Info

Product

Resources

About