More on “SOA, Agile, and TDD”
Share tests? How is that done? How does a .NET person share their test with a legacy COBOL person?
The SDWest event was held this week, and it appears that one of the highlights was Amr Elssamadisy’s tutorial on how agile, test-driven development methodologies are applicable in a SOA. The article reviewing his session can be found here. Amr points out a fundamental problem of code ownership for web services developers:
"“Agile requires that you fix what you break. So if you change the service your team is writing, you must fix whatever that change breaks in the clients using that service. You're responsible for your own messes. SOA, on the other hand, usually assumes that there be no collective code ownership. So you can't fix someone else's code. What's needed is a way for the team developing the service to run a test to see if their change will break any clients. If they don't own the code, then how does this happen? Through the sharing of tests.”
"
We totally agree with Amr. But, share tests? How is that done? How does a .NET person share their test with a legacy COBOL person? These arguments perfectly highlight a lot of the thinking around what Mindreef builds. We believe that this level of SOA quality is around the interfaces between services and the semantic ways that those services are used. We have built our tests independent of the language or platform they were implemented on. This way anyone can understand the tests and add to them. As a server we are always on, which means when there is a new consumer to a service (which may be months after the service is deployed) they can add to the test suites for that service to show how they semantically use that service. So now when the service is updated, they are running a larger set of test suites that include all of their consumers and users can actually know if they are breaking any of them. It also means that if a service does not work the way a consumer wishes, they can produce a test that shows what they need, which can then act as TDD for the next iteration of the service.
Now if we could only figure out Load Driven Development (LDD)…..
Trackback URL for this post: http://www.webservices.org/trackback/id/83621






Collaborating on SOA Testing isn't Optional
Jason English
Thursday 05 April 2007