Book Image

Mastering SoapUI

By : Pranai Nandan, Surendra Mohan
Book Image

Mastering SoapUI

By: Pranai Nandan, Surendra Mohan

Overview of this book

SoapUI is an open-source cross-platform testing application that provides complete test coverage and supports all the standard protocols and technologies. This book includes real-time examples of implementing SoapUI to achieve quality and business assurance. Starting with the features and functionalities of SoapUI, the book will then focus on functional testing, load testing, and security testing of web services. Furthermore, you will learn how to automate your services and then design data-driven, keyword-driven, and hybrid-driven frameworks in SoapUI. Then the book will show you how to test UIs and services using SoapUI with the help of Selenium. You will also learn how to integrate SoapUI with Jenkins for CI and SoapUI test with QC with backward- and forward-compatibility. The final part of the book will show you how to virtualize a service response in SoapUI using Service Mocking. You will finish the journey by discovering the best practices for SoapUI test automation and preparing yourself for the online certification of SoapUI.
Table of Contents (18 chapters)
Mastering SoapUI
About the Author
About the Reviewer
SoapUI Integration with Jenkins and HP QC

Chapter 9. Service Mocking

As we move forward with test automation of SOA based applications we face several challenges to automate business flows. A few of these challenges can be answered by service virtualization and service mocking.

Service virtualization is a matured and a more detailed process to help in testing and test automation, whereas in service mocking stubs are made by considering test cases or test suites.

In this chapter we will learn how to create a mock service with different techniques/dispatch methods and deploy them.

So, before we move forward, we may well ask why we need service virtualization or service mocking.

Let's take a look at a few of the challenges faced during SOA testing and test automation:

  • No access to the third-party service

  • All the services are not ready, hence integration cannot be tested

  • Dependency on an external system which is not in control of the test team

  • Cost to be paid for accessing certain systems in the test environment

Because of the preceding issues...