There's not a lot of talk about software testing in an SOA, maybe because it's so complicated. Even in a simple database that's part of, say, an order processing application, you have to expose the application code as a service, make sure it does what it's supposed to do, make sure it doesn't do anything you don't know about, regression test the original database, stress test the service, acceptance test it—and that's only one service. It gets worse with composite applications.Read "SOA and Software Testing" at IT-Director.com.
Copyright © 2006 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Friday, August 04, 2006
More than once on my SOA journey I have wondered to myself and out loud "How on earth do we test this stuff?" with the "stuff" meaning an SOA infrastructure or an SOA-based application. Intuitively I have always thought that the testing strategy must have to be different. One of my numerous email newsletter subscriptions ( IT Business Edge Hot Story )caught my eye the other day with the catchy title "The Pitfalls of SOA Software Testing." Its worth taking a look: