The consequences of overlooking SOA testing blind spots

Colleen Frye, News Writer for SearchSoftwareQuality.com published a valuable article on the consequences of overlooking SOA Testing Blindspots. Rizwan Mallal, quoted in this article, highlights a couple of solid technical points:

1. HTTP 200 codes, although important in web site testing, are insufficient for web services testing that requires deeper content inspection to decide whether a request-response pair is successful.
2. Simply sending the same message over and over again is Performance Testing is incorrect and flawed. Most endpoints enforce security that requires message uniqueness and detect for message replay-type attacks. Most testing tools that started as web application testing tools lack web services testing features and are inadequate for SOA Testing.

SOAPSonar from Crosscheck Networks, unlike other products in the industry is built ground-up for SOA/Web Service Testing and has all the XML, SOAP, WSDL, WS-Security, WS-Trust, MTOM type standards that are inherently available for functional, performance, interoperability and security testing with a very simple to use user interface that doesn't require an army of consultants to install and configure. Plus Crosscheck provides a Personal Edition of the product for free.

For a detailed article on SOA Testing Blindspots see: Watch your SOA Testing Blindspots

SOA Magazine - On SOA Testing

Thomas Erl, a thought leader and specialist of everything SOA, author of Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services" and "Service-Oriented Architecture: Concepts, Technology, and Design, " - both books international bestsellers, is the Site Editor and Series Editor for The SOA Magazine, a monthly online publication provided by SOA Systems Inc. and Prentice Hall/PearsonPTR and is officially associated with the "Prentice Hall Service-Oriented Computing Series from Thomas Erl."

Watch your SOA Blind Spots is published in the latest edition of The SOA Magazine. Web services testing techniques have been around for some time. However, with the increased utilization of Web services within service-oriented solutions, the demands and complexities placed on Web services are being taken to a new level. This is in sharp contrast to traditional RPC applications and integration architectures wherein the role of Web services was typically limited to point-to-point data exchanges. Now, Web services find themselves being reused across multiple service compositions and in the midst of dynamic and sophisticated runtime service activities and chains. This article raises a series of testing issues and provides recommended techniques and remedies for establishing robust Web services-based SOA implementations...

The SOA Magazine: http://www.soamag.com/default.asp

Watch your SOA Blind Spots: http://www.soamag.com/I8/0607-2.asp

Watch your SOA Testing Blind Spots

This latest article by Crosscheck Networks' R&D team highlights various common SOA Blind Spots that SOA testers experience in real-life deployments.

The Blind Spots and remedies focus on the following areas:

1. Performance
2. Security
3. SOAP Attachments
4. WSDL
5. Interoperability

For these 5 areas of SOA Testing, the article describes how to identify common SOA blind spots and techniques for avoiding them.

The full article (PDF), can be downloaded here: Watch your SOA Testing Blind Spots