Tony Vu, Puppet Labs
Assembling and building your own RESTful wrappers for testing services gives you the opportunity to share your tool with other elements of your organization, such as other quality engineers or other development engineers not familiar with your product space. The upfront cost will be higher than implementing a commercial service to test your API, but the resulting library will eliminate the siloing effect of isolated test code and tools, unusable by other members of your organization. For the purposes of this paper, we will consider RESTful wrappers to be a kind of library, and will use the term ‘“library” and “tool” to mean “RESTful wrapper” unless otherwise specified.
This paper is organized into two sections:
- An argument for quality engineers to create RESTful Wrappers meant to be shared with cross-functional teams.
- An in-depth study of building such a library for RESTful services.
Target Audience: Advanced