1. SOA Testing Experience Report IWST 2008
Ken Ahrens
© 2007, iTKO, Inc. | PROPRIETARY / CONFIDENTIAL
W W W . I T K O . C O M

2. SOA Testing Common Themes
SOA is not web services
9 out of 10 web services also involve some other type of technology
Agile development and SOA
Rapid changes upset the traditional testing model
Unit tests often don’t make their way to QA (and vice versa)
End-to-end testing becoming a business requirement
Working with the UI no longer deep enough for QA
SOA governance and testing
Enhancing UDDI to add validation (Governance with teeth)
Constrained environments
Vmware vs. Mock Services vs. Service Oriented Virtualization

3. “Three C’s” of SOA Testing
Complete Testing
Every heterogeneous layer of architecture, in context
No coding – point and click testing
Reuse functional test for performance testing
Collaborative Testing
Test early before UIs are created
Virtual Services
Single solution for dev testing, integration, regression, and performance testing
Continuously Test
Regress on existing functionality
Add testing of new services to existing testing workflows
Complete
single component  all technologies
Collaborative
Dev/QA test silos  everyone tests, every phase
Continuous
Phased tests  constant testing 3

4. Screenshot: Message Testing

5. Screenshot: Reporting

6. Screenshot: Virtual Services