Automating property-based testing of evolving web services

Abstract

Web services are the most widely used service technology that drives the Service-Oriented Computing (SOC) paradigm. As a result, effective testing of web services is getting increasingly important. In this paper, we present a framework and toolset for testing web services and for evolving test code in sync with the evolution of web services. Our approach to testing web services is based on the Erlang [5, 9] programming language and QuviQ QuickCheck, a property-based testing tool written in Erlang, and our support for test code evolution is added to Wrangler, the Erlang refactoring tool.The key components of our system include the automatic generation of initial test code, the inference of web service interface changes between versions, the provision of a number of domain specific refactorings and the automatic generation of refactoring scripts for evolving the test code. Our framework provides users with a powerful and expressive web service testing framework, while minimising users' effort in creating, maintaining and evolving the test model. The framework presented in this paper can be used by both web service providers and consumers, and can be used to test web services written in whatever language; the approach advocated here could also be adopted in other property-based testing frameworks and refactoring tools.

Property-based testing of web services by deriving properties from business-rule models

“…A similar approach was presented by Li et al [19]. They also show how WSDL can be used to automatically derive generators, but the focus of their work is primarily on evolving web services.…”

QuickREST: Property-based Test Generation of OpenAPI-Described RESTful APIs

“…For web services, as we target, PBT have been used for services implementing Web Services Description Language (WSDL) specifications, translating the specification to generators and properties [25]- [27]. For REST services Seijas et al proposed PBT, however according to the authors this was a highly manual approach [28].…”