Skip to main navigation Skip to search Skip to main content

Towards a metamorphic testing methodology for service-oriented software applications

Research output: Chapters, Conference Papers, Creative and Literary WorksRGC 32 - Refereed conference paper (with host publication)peer-review

Abstract

Testing applications in service-oriented architecture (SOA) environments needs to deal with issues like the unknown communication partners until the service discovery, the imprecise black-box information of software components, and the potential existence of non-identical implementations of the same service. In this paper, we exploit the benefits of the SOA environments and metamorphic testing (MT) to alleviate the issues. We propose an MT-oriented testing methodology in this paper. It formulates metamorphic services to encapsulate services as well as the implementations of metamorphic relations. Test cases for the unit test phase is proposed to generate follow-up test cases for the integration test phase. The metamorphic services will invoke relevant services to execute test cases and use their metamorphic relations to detect failures. It has potentials to shift the testing effort from the construction of the integration test sets to the development of metamorphic relations. © 2005 IEEE.
Original languageEnglish
Title of host publicationProceedings - International Conference on Quality Software
Pages470-476
Volume2005
DOIs
Publication statusPublished - 2005
Externally publishedYes
Event5th International Conference on Quality Software, QSIC 2005 - Melbourne, Australia
Duration: 19 Sept 200520 Sept 2005

Publication series

Name
Volume2005
ISSN (Print)1550-6002

Conference

Conference5th International Conference on Quality Software, QSIC 2005
PlaceAustralia
CityMelbourne
Period19/09/0520/09/05

Research Keywords

  • Integration testing
  • Metamorphic testing infrastructure
  • Service-oriented architecture
  • Unit testing

Fingerprint

Dive into the research topics of 'Towards a metamorphic testing methodology for service-oriented software applications'. Together they form a unique fingerprint.

Cite this