Analogies and differences between mutation operators for WS-BPEL 2.0 and other languages

Juan Boubeta-Puig*, Inmaculada Medina-Bulo, Antonio García-Domínguez

*Corresponding author for this work

Research output: Chapter in Book/Published conference outputConference publication

Abstract

Applying mutation testing to a program written in a certain language requires that a set of mutation operators is defined for that language. The mutation operators need to adequately cover the features of that language in order to be effective. In this work, we evaluate qualitatively the operators defined for the Web Services Business Process Execution Language 2.0 (WS-BPEL) and study the differences and similarities between WS-BPEL and other languages. We review the existing operators for several structured and object oriented general-purpose programming languages, and for several domain-specific languages. Results confirm that WSBPEL is very different from other languages, as half of the mutation operators for this language are equivalent to those of other languages. Our study concludes that the set of WS-BPEL mutation operators can be improved.

Original languageEnglish
Title of host publicationProceedings - 4th IEEE International Conference on Software Testing, Verification, and Validation Workshops, ICSTW 2011
Pages398-407
Number of pages10
DOIs
Publication statusPublished - 18 Aug 2011
Event4th IEEE International Conference on Software Testing, Verification, and Validation Workshops, ICSTW 2011 - Berlin, Germany
Duration: 21 Mar 201125 Mar 2011

Conference

Conference4th IEEE International Conference on Software Testing, Verification, and Validation Workshops, ICSTW 2011
Country/TerritoryGermany
CityBerlin
Period21/03/1125/03/11

Keywords

  • Mutation analysis
  • Mutation operators
  • Test-suite effectiveness
  • Testing
  • Web services
  • WS-BPEL

Fingerprint

Dive into the research topics of 'Analogies and differences between mutation operators for WS-BPEL 2.0 and other languages'. Together they form a unique fingerprint.

Cite this