Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • SoapUI Cookbook
  • Toc
  • feedback
SoapUI Cookbook

SoapUI Cookbook

By : Rupert Anderson
4 (5)
close
SoapUI Cookbook

SoapUI Cookbook

4 (5)
By: Rupert Anderson

Overview of this book

This book is aimed at developers and technical testers who are looking for a quick way to take their SoapUI skills and understanding to the next level. Even if you are new to SoapUI but have basic Java skills and a reasonable grasp of RESTFul and Soap web services, then you should have no problem making use of this book.
Table of Contents (13 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Sections
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Testing and Developing Web Service Stubs With SoapUI
chevron up
1. Testing and Developing Web Service Stubs With SoapUI
Introduction
Generating a WSDL-first web service using SoapUI tool integration
Developing a SOAP web service test-first
Updating a SOAP project using a WSDL
Updating SOAP projects using WSDL refactoring (Pro)
Generating and developing a RESTful web service stub test-first
Generating SoapUI tests with REST discovery (Pro)
2
2. Data-driven Testing and Using External Datasources
2. Data-driven Testing and Using External Datasources
Introduction
Creating and checking data with the JDBC Request TestStep
Parameterizing SQL queries with the JDBC Request TestStep
Setting properties from an external file
Importing CSV file data into an in-memory H2 database with Groovy
Looping over CSV file data and driving tests with Groovy
Querying MongoDB with Groovy
Publishing, browsing, and consuming ActiveMQ JMS messages via the REST API
3
3. Developing and Deploying Dynamic REST and SOAP Mocks
3. Developing and Deploying Dynamic REST and SOAP Mocks
Introduction
Selecting mock responses using Groovy
Developing dynamic database-driven SOAP mocks
Developing dynamic database-driven REST mocks
Building mock responses dynamically
Deploying mocks as WAR files
4
4. Web Service Test Scenarios
4. Web Service Test Scenarios
Introduction
Testing WSDL and response WS-I compliance
Testing SOAP response schema compliance
Testing REST response XML schema compliance
Testing response compliance using JSON schemas
Testing and mocking SOAP (MTOM+XOP) attachments
Testing HATEOAS links
Testing polling style asynchronous REST services
Testing asynchronous SOAP service callbacks
Testing for e-mails with Groovy
Testing files with Groovy
5
5. Automation and Scripting
5. Automation and Scripting
Introduction
Running mocks from the command line
Running tests from the command line
Providing environment-specific properties
Generating mock WAR files from the command line
Running mocks and tests using Maven
Running mocks and tests using Java and JUnit
Running mocks and tests using Groovy scripts
Running mocks and tests using Gradle
6
6. Reporting
6. Reporting
Introduction
Generating reports from test runners
Publishing JUnit reports using Jenkins
Exporting custom reports using Groovy
Analyzing test, HTTP, and mock coverage (Pro)
7
7. Testing Secured Web Services
7. Testing Secured Web Services
Introduction
Testing basic HTTP-authenticated RESTful web services
Testing HTTP Digest-authenticated RESTful web services
Testing HTTP form-authenticated RESTful web services
Creating and using X.509 certificates to test web services over HTTPS
Testing client certificate authenticated web services
Securing mock services using X.509 certificates
Testing WS-Security UsernameToken, Timestamp, and TransportBinding
Scanning web service security vulnerabilities
8
8. Testing AWS and OAuth 2 Secured Cloud Services
8. Testing AWS and OAuth 2 Secured Cloud Services
Introduction
Testing Dropbox using a pregenerated OAuth 2 Access Token
Testing Dropbox using OAuth 2 Authorization Code Grant flow
Testing Dropbox using OAuth 2 Implicit Grant flow
Testing the Gmail API using OAuth2
Automating OAuth 2 authentication and consent
Testing AWS services using Access Key authentication
9
9. Data-driven Load Testing With Custom Datasources
9. Data-driven Load Testing With Custom Datasources
Introduction
Load testing data-driven TestCases concurrently with separate Groovy datasources
Load testing data-driven TestCases concurrently with a shared Groovy datasource
Load testing data-driven TestCases concurrently with a shared distributed datasource
Running load tests using Maven, command line, Java, Groovy, and Gradle scripts
10
10. Using Plugins
10. Using Plugins
Introduction
Using old-style (open source) plugins
Sending e-mails with the Email TestStep plugin
Using plugins via the plugin manager (Pro)
Using the Groovy Console plugin to create and run a new TestStep
Packaging old-style plugins when running tests with Maven
11
11. Taking SoapUI Further
11. Taking SoapUI Further
Introduction
Building, packaging, and running SoapUI from the source code
Importing, building, running, and debugging SoapUI in Eclipse
Developing a Groovy plugin with custom Action using Gradle
Logging from extensions and scripts
Prompting for user input with the UISupport class
Creating a custom RequestFilter (Listener) plugin
Creating a custom TestStep (Factory) plugin to check whether a file exists
12
Index
Index

Updating SOAP projects using WSDL refactoring (Pro)

Updating a SOAP project's WSDL will often lead to changes to test endpoints, requests, responses, and/or operations. In a simple example like that of the previous recipe, this isn't a big deal. For more complex WSDL changes that involve more tests, SoapUI Pro has a nice graphical editor that manages the migration step by step.

SoapUI WSDL refactoring can help manage the following:

  • Adding, removing, or renaming operations
  • Adding, removing, or renaming request/response fields
  • Resulting XPath (Assertion) updates

Getting ready

We'll work on the <chapter1 samples>/invoice-soap-v2-soapui-project.xml project from the previous recipe. I have also included the project <chapter1 samples>/Invoice-soap-v3-soapui-project.xml, which is the end product after the refactoring.

The new WSDL can be found at <chapter1 samples>/soap/invoicev3/wsdl/invoice_v3.wsdl.

How to do it...

To illustrate the WSDL refactoring functionality, we'll refactor invoice_v2.wsdl and the tests from the previous recipe to use a new WSDL invoice_v3.wsdl. This will involve the following changes:

  • The getInvoice operation gets renamed to retrieveInvoice
  • New operations such as updateInvoice and deleteInvoice are added
  • The invoiceNo field is renamed to id
  • A new field dueDate is added to the invoice document
  • The companyName field is removed in favor of a new customerRef field

These changes will result in a CRUD style interface, with some basic schema changes:

  1. Firstly, open the project (the previous recipe's project: InvoiceSOAPv3) and right-click on InvoiceServicePortBinding and select RefactorDefinition. Enter the path to the new WSDL (invoice_v3.wsdl) and tick the options to create new requests and a backup, and then click on Next.
  2. In the Transfer Operations window, SoapUI correctly maps createInvoice and leaves getInvoice in red to indicate that it has no mapping in the new WSDL. Correct this by clicking and dragging getInvoice on top of retrieveInvoice in the New Schema section, to end up with a result as shown in the following screenshot:
    How to do it...
  3. Click on Next to proceed to the Refactor Schema window. Correct the getInvoice request in a similar way as shown here:
    How to do it...
  4. Then, click on the red createInvoice operation. Here, map invoiceNo to id, but company cannot be mapped (as we are removing it), so highlight it and click on Discard. Things should look like what is shown in the following screenshot; when ready, click on Next:
    How to do it...
  5. On the Update XPath Expressions window, first click on Filter unchanged paths to show only the problems. We can't fix the XPath relating to companyName, so just fix the invoiceNo XPath's Assertion InvoiceNoShouldBe12345 by copying the Old XPath value into the New Xpath box and changing invoiceNo to id (as shown in the next screenshot), and then click on Finish:
    How to do it...
  6. Click on Yes in the Update Definition pop up to update the requests with the new v3 endpoint. You should see the Update of interface successful message. This indicates that the refactoring is complete!

On inspection of the refactored SoapUI project, all artifacts appeared to be in order, with the following exceptions:

  • The endpoints in the TestSteps need to be manually updated to the v3 endpoint.
  • The automatic backup failed with an IOException (on MacOSX). As a workaround, I recommend that you manually back up the SoapUI project XML file.
  • The Assertion Invoice12345ShouldHaveCompanyNameOfTestCompany option needs to be deleted manually.

Note

Passing The Tests

If you would like to see the tests pass again, you can generate a v3 invoice service as per the previous recipes. Then, add a minimal implementation to satisfy the current assertions. I have included a very basic implementation <chapter1 samples>/soap/invoicev3_impl, which can just be run in the same way as the first three recipes.

There's more...

The refactoring tool obviously doesn't write the missing tests for the updateInvoice and deleteInvoice operations or create Assertions for the new fields. These need to be added manually to return to an acceptable level of test coverage.

In terms of possible uses for WSDL refactoring, three typical SOA patterns are:

Variations on the first pattern are perhaps the most common, that is, refactoring of a single WSDL, as per our example. This is also the only pattern that can be covered in a single pass of the WSDL refactoring feature.

End of Section 6
Next Section
bookmark search playlist download
font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete