Compositional Testing with ioco

  • Machiel van der Bijl
  • Arend Rensink
  • Jan Tretmans
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2931)


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.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Tretmans, J.: Test generation with inputs, outputs and repetitive quiescence. Software— Concepts and Tools 17, 103–120 (1996)zbMATHGoogle Scholar
  2. 2.
    Tretmans, J.: Testing concurrent systems: A formal approach. In: Baeten, J.C.M., Mauw, S. (eds.) CONCUR 1999. LNCS, vol. 1664, pp. 46–65. Springer, Heidelberg (1999)CrossRefGoogle Scholar
  3. 3.
    Fernandez, J.C., Jard, C., Jéron, T., Viho, C.: An experiment in automatic generation of test suites for protocols with verification technology. Science of Computer Programming – Special Issue on COST247, Verification and Validation Methods for Formal Descriptions 29, 123–146 (1997)Google Scholar
  4. 4.
    He, J., Turner, K.: Protocol-Inspired Hardware Testing. In: Csopaki, G., Dibuz, S., Tarnay, K. (eds.) Int.Workshop on Testing of Communicating Systems 12, pp. 131–147. Kluwer Academic Publishers, Dordrecht (1999)Google Scholar
  5. 5.
    Belinfante, A., Feenstra, J., Vries, R.d., Tretmans, J., Tretmans, J., Goga, N., Feijs, L., Mauw, S., Heerink, L.: Formal test automation: A simple experiment. In: Csopaki, G., Dibuz, S., Tarnay, K. (eds.) 12thInt. Workshop on Testing of Communicating Systems, pp. 179–196. Kluwer Academic Publishers, Dordrecht (1999)Google Scholar
  6. 6.
    Petrenko, A., Yevtushenko, N.: Fault detection in embedded components. In: Kim, M., Kang, S., Hong, K. (eds.) Tenth Int. Workshop on Testing of Communicating Systems, pp. 272–287. Chapman & Hall, Boca Raton (1997)Google Scholar
  7. 7.
    ISO/IEC JTC1/SC21WG7, I.-TU-T SG 10/Q.8: Information Retrieval, Transfer and Management for OSI; Framework: Formal Methods in Conformance Testing. Committee Draft CD 13245-1, ITU-T proposed recommendation Z.500. ISO – ITU-T, Geneve (1996)Google Scholar
  8. 8.
    Jard, C., Jéron, T., Tanguy, L., Viho, C.: Remote testing can be as powerful as local testing. In: Formal Desciption Techniques and Protocol Specification, Testing and Verification FORTE XI /PSTV XVIII 1999. Kluwer Academic Publishers, Dordrecht (1999)Google Scholar
  9. 9.
    Petrenko, A., Yevtushenko, N., Von Bochman, G.: Fault models for testing in context. In: Gotzhein, R., Bredereke, J. (eds.) Proceedings FORTE. IFIP Conference, vol. 69, pp. 163–178. Kluwer, Dordrecht (1996)Google Scholar
  10. 10.
    De Nicola, R., Segala, R.: A process algebraic view of Input/Output Automata. Theoretical Computer Science 138, 391–423 (1995)zbMATHCrossRefMathSciNetGoogle Scholar
  11. 11.
    Petrenko, A., Bochmann, G.: Conformance relations and test derivation. In: Rafiq, O. (ed.) Sixth Int. Workshop on Protocol Test Systems. IFIP Transactions, vol. C-19, pp. 157–178. North-Holland, Amsterdam (1994)Google Scholar
  12. 12.
    van der Bijl, M., Rensink, A., Tretmans, J.: Component based testing with ioco. Technical report, University of Twente (2003),
  13. 13.
    Brookes, S.D., Hoare, C.A.R., Roscoe, A.W.: A theory of communicating sequential processes. Journal of the Association for Computing Machinery 31, 560–599 (1984)zbMATHMathSciNetGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Machiel van der Bijl
    • 1
  • Arend Rensink
    • 1
  • Jan Tretmans
    • 2
  1. 1.Software Engineering, Department of Computer ScienceUniversity of TwenteEnschedeThe Netherlands
  2. 2.Software Technology Research GroupUniversity of NijmegenNijmegenThe Netherlands

Personalised recommendations