Web Services Testing – 3 Days

-

Web Services Testing – 3 Days

PREREQUISITES:
Must have knowledge of Manual testing
Good to know (but not necessary) basic knowledge of Groovy, Eclipse Site
(It is mandatory to accomplish the training prerequisite conditions before nominating for the session)
PROGRAM OVERVIEW
All topics are introduced by examples and real-life experience learning, the topics are inclusive of learning by workshop and hands-on session. Certain topics are elaborated with live Case Studies to elaborate the subject matter
SKILLS GAINED BY THIS COURSE 
  • Manual Software Testing Techniques for Web Services
  • Automation testing of Web Services using SOAP UI and REST API Testing
COURSE DESIGNED FOR 
  • Software Test Professionals, QA Managers and Architects, QA Specialists
  • Manual Testers, Software Quality Control Engineers, Test Leads
COURSE DELIVERY**
Schedule  Topics
Day 1       Module 1 – 2
Day 2       Module 3 – 4
Day 3       Module 5 – 6
** All Modules listed are covered during Workshop. However, Module Coverage and Day-wise coverage may vary based on Participants Need and Skillset. Some Modules may be covered early or later while some may require greater detailing than other modules. Day-wise break-up of Modules is only indicative, not to be considered as de-facto.
1.0Introduction to Workshop
Webservices and SoapUI
Mix: Introduction
  • Web Services Testing and SoapUI Concepts
  • Alternatives to SOAP
  • Introduction to WSDL
  • Message Exchanging Patterns
  • Approaches to testing web services
    • Unit, Functional, Integration, Performance
  • Challenges in testing Web Services
  • Practicals: Testing Web Services Manually
  • Introduction to Web Services testing using tools
  • How tools and manual testing services complement each
2.0SoapUI
What is SoapUI? 
Use of SoapUI 
Features of SoapUI 
Practicals: Setup SoapUI on Windows
Understand the terms in WSDL
3.0 Practicals: SoapUI Project
Creating SoapUI Project
SOAP requests and responses
Practicals: Using SoapUI
  • Create Project
  • Create Test Suite
  • Add Test Cases
  • Run Test Suite
  • Working with Test Cases
    • Reading values from file
    • Transfer properties between test steps
  • Performance testing using SoapUI
    • Types of Load Tests – Simple, Burst, Thread, Variance
  • 4.0 Practicals: Execute Performance Test
Run a performance test
Load test report analysis
Load test assertions in SoapUI
5.0  Practicals: SoapUI Advanced
Scripting in SoapUI
  • Introduction to Groovy
Practicals: Using Groovy
  • Hello Groovy first program
  • Variable, object declaration
  • Control structures
  • Class and method declarations
  • Setup, Teardown, Assertions
  • test Runner
Automated testing using SoapUI
Some SoapUI Plugins
6.0 REST Testing
Introduction to REST
  • Test REST APIs using SoapUI
  • Functional Testing of REST services
  • WADL

Comments

Post a Comment

Popular posts from this blog

Cloud Computing in simple

-
Cloud Computing =   Infrastructure as a Service (IaaS) + Platform as a Service (PaaS) + Software as a Service (SaaS) Cloud computing, also known as Cloud Technology, Cloud Applications or Cloud-based services. Cloud Computing is the practice of using a network of remote servers hosted on the internet to store, manage and process data, rather than a local server or a personal computer. Examples of cloud-based services include customer self-scheduling, data storage, online payment, and accounting software Different Type of Clouds Infrastructure as a Service (IaaS)  – Allows users with the services like Virtual servers, Virtual storage, Physical Database, Virtual Network, Physical Network. E.g. Google Storage ,  IBM Cloud Computing ,  Nimbus Platform as a Service (PaaS)  – Provides computational resources via a platform upon which applications and services can be developed and hosted. E.g. Databases, Data Stores,  Force.com ,  Google App Engine ,  Windows Azure  (Platform). Soft
Read more

How to Write an Effective Design Document

-
Image
How to Write an Effective Design Document Why write a design document? A design document is a way for you to communicate to others what your design decisions are and why your decisions are good decisions. Don’t worry if your design is not UML compliant and don’t worry if you didn’t use a special modeling tool to create it. The biggest factor that determines if your design document is good is whether or not it clearly explains your intentions. This presents a problem, however. In order to convey design decisions, you have to consider the audience that you are writing for. A peer developer will understand why a well-crafted class abstraction is a good design, however your manager will probably not. Because your peer developers and your manager have different concepts of what makes a design good, there is a need for two design documents; one for peer developers and one for managers. Each document serves a different and equally valuable purpose as you begin your project development. I
Read more

Bookmark

-
Good Blog about Architecture & design Patterns:   http://martinfowler.com/bliki/ http://www.sharepoint-videos.com/ http://go.cloudshare.com/Linkedin_ProPlus_SharePoint.html A Technical Q/A site: http://www.bookmarkresource.com http://blog.krisvandermast.­ com/ASPNET20PageLifeCycle.aspx http://blogs.vertigosoftware.­ com/shannonf/archive/2005/08/­ 07/1355.aspx http://john-sheehan.com/blog/­ net-cheat-sheets/ http://www.eggheadcafe.com/­ articles/20051227.asp http://duartes.org/gustavo/­ articles/Asp.net-Runtime-­ Cheat-Sheet-HttpRequest-­ HttpRuntime.aspx http://www.addedbytes.com/­ cheat-sheets/javascript-cheat- ­sheet/ http://www.antsmagazine.com/­ 2009/04/100-useful-cheat-­ sheets-for-web-designers-­ developers/ Nice link abt .Net 3.5: http://www.simple-talk.com/ dotnet/.net-framework/.net-3. 5-language-enhancements/ nice articles about JQuery. http://encosia.com/2008/05/29/ using-jquery-to-directly-call- aspnet-ajax-page-methods/ http://encosia.co
Read more