Web services automation workshop sreedhar dakshinamurthy

527 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
527
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Web services automation workshop sreedhar dakshinamurthy

  1. 1. May 2013 SOAP based WebServices: Automation without SOAP UI
  2. 2. SOAP based WebServices: Automation without SOAP UI: THOUGHTWORKS INDIA PVT LTD
  3. 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. 4. Why WebServices: Main Frame Data Business Logic Presentation Terminal 1 Terminal 2 Terminal 3 Terminal 4 Simple Scalability Pro’s Con’s
  5. 5. Why WebServices: Client/Server Data Business Logic PC 1 PC 2 PC 3 PC 4 Scalability Maintenance Pro’s Con’s
  6. 6. Why WebServices: Three Tier Data Scalability Complex App Server PC’s Pro’s Con’s
  7. 7. Why WebServices: SOA Data Simple Web Services PC’s
  8. 8. WebServices •  REST Based WebServices •  SOAP Based WebServices SOAP (Simple Object Access Protocol) WSDL (Web Services Description Language)
  9. 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. 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. 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. 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. 13. Contact us Sreedhar Dakshinamurthy +91-9880722880 sdakshin@thoughtworks.com www.thoughtworks.com

×