Book Image

Mastering SoapUI

Book Image

Mastering SoapUI

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
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
7
SoapUI Integration with Jenkins and HP QC
Index

Implementing a real world test case using SoapUI and Selenium together


Scenario: Verify if a customer is able to pay his credit card bill.

The Flow as follows:

  1. User logs in.

  2. User enters details on the UI page and clicks Submit; a unique ID is generated and shown on the UI with status: in Progress, and asks for a token to process the payment.

  3. Service A is called and the request of service A needs the unique ID generated to be passed in the request.

  4. Service B is called.

  5. Service C creates the new token.

  6. The user needs the token created by service C to complete the transaction as he needs to enter it in the UI.

  7. The user enters the token and clicks on the Submit button.

  8. The user receives a message payment is done.

So in the previous example we have eight steps, five of the steps are from the UI and three are from the services side. We also see that there is a need to transfer data from the UI to the service request and vice versa.

Now let's assume we need to assert certain UI elements on the screen as...