Compositional Testing with ioco

A. Petrenko; H.M. van der Bijl; Arend Rensink; A. Ulrich; G.J. Tretmans

doi:10.1007/b95400

Compositional Testing with ioco

A. Petrenko (Editor), H.M. van der Bijl, Arend Rensink, A. Ulrich (Editor), G.J. Tretmans

Research output: Contribution to conference › Paper › peer-review

93 Citations (Scopus)

283 Downloads (Pure)

Abstract

Abstract. Compositional testing concerns the testing of systems that consist of communicating components which can also be tested in isolation. Examples are component based testing and interoperability testing. We show that, with certain restrictions, the ioco-test theory for conformance testing is suitable for compositional testing, in the sense that the integration of fully conformant components is guaranteed to be correct. As a consequence, there is no need to re-test the integrated system for conformance. This result is also relevant for testing in context, since it implies that every failure of a system embedded in a test context can be reduced to a fault of the system itself.

Original language	Undefined
Pages	86-100
Number of pages	15
DOIs	https://doi.org/10.1007/b95400 https://doi.org/10.1007/978-3-540-24617-6_7
Publication status	Published - 2004
Event	Formal Approaches to Software Testing (FATES) - Duration: 1 Jan 2004 → 1 Jan 2004

Workshop

Workshop	Formal Approaches to Software Testing (FATES)
Period	1/01/04 → 1/01/04

Keywords

IR-66359
EWI-6928

Access to Document

Cite this

@conference{cef61468bf9446ddb32acf626a8b8c71,

title = "Compositional Testing with ioco",

abstract = "Abstract. Compositional testing concerns the testing of systems that consist of communicating components which can also be tested in isolation. Examples are component based testing and interoperability testing. We show that, with certain restrictions, the ioco-test theory for conformance testing is suitable for compositional testing, in the sense that the integration of fully conformant components is guaranteed to be correct. As a consequence, there is no need to re-test the integrated system for conformance. This result is also relevant for testing in context, since it implies that every failure of a system embedded in a test context can be reduced to a fault of the system itself.",

keywords = "IR-66359, EWI-6928",

author = "A. Petrenko and {van der Bijl}, H.M. and Arend Rensink and A. Ulrich and G.J. Tretmans",

year = "2004",

doi = "10.1007/b95400",

language = "Undefined",

pages = "86--100",

note = "Formal Approaches to Software Testing (FATES) ; Conference date: 01-01-2004 Through 01-01-2004",

}

TY - CONF

T1 - Compositional Testing with ioco

AU - van der Bijl, H.M.

AU - Rensink, Arend

AU - Tretmans, G.J.

A2 - Petrenko, A.

A2 - Ulrich, A.

PY - 2004

Y1 - 2004

N2 - Abstract. Compositional testing concerns the testing of systems that consist of communicating components which can also be tested in isolation. Examples are component based testing and interoperability testing. We show that, with certain restrictions, the ioco-test theory for conformance testing is suitable for compositional testing, in the sense that the integration of fully conformant components is guaranteed to be correct. As a consequence, there is no need to re-test the integrated system for conformance. This result is also relevant for testing in context, since it implies that every failure of a system embedded in a test context can be reduced to a fault of the system itself.

AB - Abstract. Compositional testing concerns the testing of systems that consist of communicating components which can also be tested in isolation. Examples are component based testing and interoperability testing. We show that, with certain restrictions, the ioco-test theory for conformance testing is suitable for compositional testing, in the sense that the integration of fully conformant components is guaranteed to be correct. As a consequence, there is no need to re-test the integrated system for conformance. This result is also relevant for testing in context, since it implies that every failure of a system embedded in a test context can be reduced to a fault of the system itself.

KW - IR-66359

KW - EWI-6928

U2 - 10.1007/b95400

DO - 10.1007/b95400

M3 - Paper

SP - 86

EP - 100

T2 - Formal Approaches to Software Testing (FATES)

Y2 - 1 January 2004 through 1 January 2004

ER -