I stumbled across RedMonk Radio – episode 6 (via Sandy Kemsley) last week in which they talk a bit about Testing in the realm of SOA. The inspiration for the topic came from a company called Green Hat Consulting which has a product called GH Tester (Wow! Original name or what) who is not a client, but did brief them.
- In every computer revolution, there is a common pattern: Glue components together to make something greater than the sum of the parts, then ask how come it doesn’t scale?
- If Mercury is concentrating on load testing, Green Hat wants to position itself as load testing with a difference
- Or more shot-over-the-bow-ish, Mercury for the SOA world
- Questions to ask when thinking of how to approach a SOA testing problem
- What are the interfaces?
- What systems do they touch
- What are the implications that this is composite system
- I missed this particular revolution, but know enough to know that this is supposed to be funny: How do you spell SOA? CORBA
- A huge chunk of SOA is about enabling legacy systems (old line applications meet new models)
- When outsourcing development of SOA components, need to have some sort of automated compliance and auditing tool. Definitely one of those cases where you want to find breakages early.
I’m applied for access to their whitepapers, but have not yet qualified it seems. I must admit though that I can think of a few companies around that might find this product of interest; if not now, then a step or two down their roadmap. (Yes JR, I am pointing to you)