Better Software - March 2009 - (Page 33) T I stood like Ichabod Crane while the project sponsor described an upcoming project that included Web services—a technology about which I had read so many mixed stories that I had no idea if it was the wave of the future or just another passing fad. Time passed and my team successfully completed that first pilot project. We learned a lot along the way and were a bit more confident having one successful effort under our belts. New Web services projects kept coming, and with each new implementation we became more knowledgeable, adding new pro- this passage came to mind as cesses and tools to our testing toolbox. By continually refining our processes, we now have a proven strategy for testing Web services that includes four distinct testing types, each building on the previous: • Functionality testing • Compliance and interoperability testing • Security testing • Performance testing In this article, we will be working with a simple, fictitious Web service that implements the Sell Your Junk Web site. This Web service allows organizations and individuals to submit a picture (file) www.StickyMinds.com of an item to sell, a text description of the item, and the selling price. The Sell Your Junk Web service forwards information to a billing Web service called BillEm, created by another group to charge the client a posting fee. This Web service is very similar to those used by e–commerce sites that provide a way to post items for sale on their Web sites. Looking a little deeper into the Sell Your Junk Web service, we see that it sends an XML request including the file name of the picture, item price, item description, and account number and receives an XML response. The details of the request are: MARCH 2009 BETTER SOFTWARE 33 http://www.StickyMinds.com
For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.