SOAP based web services allow for communication between applications over the internet in a platform and language independent manner. While SOAP UI is commonly used to test SOAP web services, it has limitations like being non-IDE based, having limited debugging capabilities, and requiring proprietary licensing. Developing a test framework using an object-oriented language like Java addresses these limitations by providing an open source and modular approach that better integrates with development tools and continuous integration processes.

1. May 2013
SOAP based WebServices: Automation
without SOAP UI

2. SOAP based WebServices: Automation
without SOAP UI:
THOUGHTWORKS INDIA PVT LTD

3. Why Are We Here?
u Brief introduction into Why WebServices
u Basics of SOAP based WebServices
u Challenges of SOAP UI automation
u Test Framework development for a Sample
application and the advantages

4. Why WebServices: Main Frame
Data
Business Logic
Presentation
Terminal 1
Terminal 2
Terminal 3
Terminal 4
Simple
Scalability
Pro’s
Con’s

5. Why WebServices: Client/Server
Data
Business Logic
PC 1
PC 2
PC 3
PC 4
Scalability
Maintenance
Pro’s
Con’s

6. Why WebServices: Three Tier
Data
Scalability
Complex
App
Server
PC’s Pro’s
Con’s

7. Why WebServices: SOA
Data
Simple
Web
Services
PC’s

8. WebServices
• REST Based WebServices
• SOAP Based WebServices
SOAP (Simple Object Access Protocol)
WSDL (Web Services Description Language)

9. SOAP based WebServices
• SOAP stands for Simple Object Access Protocol
• SOAP is a communication protocol
• SOAP is for communication between applications
• SOAP is a format for sending messages
• SOAP is designed to communicate via Internet
• SOAP is platform independent
• SOAP is language independent
• SOAP is based on XML
What is SOAP?

10. SOAP based WebServices
• WSDL stands for Web Services Description Language
• WSDL is written in XML
• WSDL is an XML document
• WSDL is used to describe Web services
• WSDL is also used to locate Web services
What is WSDL?

11. Challenges of SOAP UI
• Coding on a Non-IDE environment
• Debugging is close to non existent
• Implementation of modularity needs extensive framework
capabilities making it non maintainable for medium – large sized
suites
• Extensively tied down to using XML
• Integration with Continuous Integration mechanism is tricky
• Proprietary Software requiring Licensing fee
Note: Demo of SOAP UI using a Local Webservice
deployed on the Presenter’s Laptop

12. Advantages
• Open Source
• Can be implemented using a Object Oriented language
• Integration with Continuous Integration mechanism is implicit
• Changing Request and Response assertion is easier in Object than
XML format
• Features of using an IDE can be used to our advantage
Note: Demo of Writing a Framework in Java using the
Local Webservice deployed on the Presenter’s Laptop

13. Contact us
Sreedhar Dakshinamurthy
+91-9880722880
sdakshin@thoughtworks.com
www.thoughtworks.com