Testing soap UI

Copyright @2014, BJIT Group. All Rights ReservedCONFIDENTIAL
API Testing in SoapUI
By
Razia Sultana
25-01-2018
Knowledge Sharing Session

Copyright @2014, BJIT Group. All Rights ReservedCONFIDENTIAL 2
Agenda
1. API
2. RESTful API
3. Difference between SOAP and REST
4. SoapUI: Introduction and Features
5. SoapUI: Download, Installation, Configuration
6. SoapUI: Create a SOAP Project, Test Suite, Test Case
7. SoapUI: Assertions
8. Functional Testing
9. Load Testing
10.Security Testing
11.API testing
12.MockService
13.Reports

API Testing
(API) Application Program Interface that is sharing data from a
program with another program.
For example: Like bell mark / canon, company made a printer for printing but they did not make
Microsoft word. How does Microsoft word print on that printer? There is definitely a relationship
between Microsoft and Canon.
Actually there is no relation between application software or printer/Canon. Two programs
communicate using an interface or medium. This medium is called API.
When have a print command in Microsoft
Word, he requests the printer status to the API,
and if all is correct, then print the document to
the API. The API asks the printer to print the
document. The printer needs to know exactly
what a program is asking to print, when a
document arrives near the printer, the printer
will read it and print it.

RESTful API Testing
(RESTful API) When Web services use REST (REpresentational state transfer)
architecture, they are called RESTful API that uses HTTP requests to GET, PUT, POST and
DELETE data.
HTTP Methods
GET: The GET method is used to retrieve data from a server at the specified resource.
POST: requests are used to send data to the API sever to create or update a resource.
PUT: requests are used to send data to the API to create or update a resource.
DELETE: method is exactly as it sounds: delete the resource at the specified URL.
The REST style emphasizes the interactions
between clients and services. REST is an
alternative to SOAP (Simple Object Access
Protocol) and instead of using XML for
request REST uses simple URL in some
cases.
Rest API supports both XML and JSON
format.

SOAP and REST - Compared
SOAP REST
1. Simple Object Access Protocol. 1. Representational State Transfer.
2. A XML based message protocol. 2. An architectural style protocol.
3. Uses WSDL for communication between
consumer and provider.
3. Uses XML & JSON to send and receive
data.
4. Invokes service by calling RPC method. 4. Simply calls via URL path.
5. Does not return human readable result. 5. Result is readable which is just plain
XML or JSON.
6. Transfer is over HTTP, SMTP or FTP
protocol.
6. Transfer is over HTTP only.
7. Javascript can call SOAP but it is difficult
to implement.
7. Easy to call from Javascript.
8. Performance is not great. 8. Performance is much better than SOAP-
less CPU intensive, leaner code etc.

Introduction- SoapUI
There are 7 important features of SOAPUI
1) Functional Testing
2) Security Testing
3) Load Testing
4) Reports
5) Supported Protocols/Technologies
6) MockService
7) API Testing
SOAPUI SOAPUI is the leading open source cross-platform API Testing tool.
It is an web service testing application for service-oriented architectures (SOA) and
representational state transfers (REST).
Its functionality covers web service inspection, invoking, development, simulation and
mocking, functional testing, load and compliance testing..

Features- SoapUI
1. Functional Testing Features
Functional Testing features (Open Source version) SOAP UI PRO
WSDL Coverage
Request/Response Coverage
Message Assertion
Test Refactoring
Running of Multiple Tests
Data Source Driven Tests
Scripting Libraries
Unit Reporting
Manual Test Step

Features- SoapUI
2. Security Testing Features
Security Testing features (Open Source version) SOAP UI PRO
Boundary Scan
Invalid Type
SQL Injection
XPath Injection
XML Bomb
Fuzzing Scan
Cross Site Scripting
Configurable Scans
Reporting

Features- SoapUI
3. Load Testing Features
Load Testing features (Open Source version) SOAP UI PRO
Rapid Load Tests from
Functional Tests
Configurable Load Strategies
Load Test Assertions
Real-Time Statistics
Performance Monitoring
Statistics Exporting
Setup/TearDown using Groovy
Scripting
loadUI Integration
Reporting

Features- SoapUI
4. Reports
Reports (Open Source version) SOAP UI PRO
JUnit Reports
Report Data Export
WSDL HTML Report
WSDL Coverage
TestSuite Coverage
TestCase Coverage
Assertion Coverage
Message Recording Coverage
JUnit Reports

Features- SoapUI
5) Supported Protocols/Technologies: SoapUI has the most comprehensive Protocol
Support

Download, Installation and Configuration - SoapUI
SoapUI is a cross-platform tool. It supports Windows, Linux, and Mac operating systems.

Download - SoapUI
Step 1 − Go to www.soapui.org and click Download SoapUI.
Download Process

Download - SoapUI
Step 2 − Click ‘Get It’ to download SoapUI Open Source. It will start downloading 112MB
.exe file in the system. Wait till the download process is complete.

Installation - SoapUI
Installation Process Step 1 − After downloading, run the .exe file as “Run as administrator”.
Windows will start the set up process as shown in the following screenshot.

.
Step 2 − Once set up, the process window displays the following screen, click
Next.
Step 3 − Accept the license agreement and click Next.

.Step 4 − Choose the installation directory or keep it as the default path
selected by the system. Click Next.

.Step 5 − Choose the components that you want to install. Click Next.

.Step 6 − Accept the License Agreement for HermesJMS and click Next.

.Step 7 − Select the target directory to save tutorials and click Next.

.Step 8 − Choose the start menu folder location or else leave the default location as is and
click 'Next'.

.Step 9 − Enable the checkbox 'create a desktop icon' and click 'Next'.
Now, the installation starts. It will take a few minutes to complete.

.Step 10 − After completion of installation, click Finish in the following wizard.
Upon clicking on Finish, SoapUI is launched.

Launched - SoapUI
.
1. Menu bar
2. Tool bar
3. Project Navigation Bar
4. Workspace Properties
5. Log Panel

Configuration - SoapUI
.
1. The first step is to create a workspace that can contain multiple projects. For Each
project, we can create several test suites.
2. For Each Test Suite, there can be several test cases attached to it.
3. For Each Test Case, there can be several test steps associated with it.

.
1. The first step is to create a workspace that can contain multiple projects. For Each
project, we can create several test suites.
2. For Each Test Suite, there can be several test cases attached to it.
3. For Each Test Case, there can be several test steps associated with it.
Step 1 − Go to File → New Workspace.

.
Step 2 − Add the name of workspace and click OK.
Step 3 − Now, select the path where workspace xml will be saved.
Step 4 − Select the path and click Save.

Configuration- SoapUI
Workspace is created as shown in the following screenshot. Workspace
properties is also exhibited.

File Menu - SoapUI
Understanding the most frequently used navigations within SOAP-UI is very
important for seamless navigation while working on real-time projects. Let us
take a look at the file menu first.
1.'New SOAP Project' allows user to create a Project by
importing SOAP Request.
2.'New REST Project' allows user to create a Project by
importing REST Request.
3.'Import Project' allows user to import the entire project by
locating the corresponding XML.
4.'Save All Projects' allows user to save all the opened
projects in a single click.
5.'Close All Open Projects' closes all the projects opened in
that workspace.
6.'Rename Workspace' allows user to rename the previously
created workspace.
7.'Switch Workspace' allows user to switch between
workspaces.
8.'Preferences' allows user to customize SOAP UI. We will
deal with it in next section.
9.'Save Preferences' allows user to save their customized
settings. When SOAP UI opened for the next time, it uses
the user saved preferences.

FILE >> PREFERENCES >> HTTP SETTINGS - SoapUI
Now, let us understand the 'Preferences' from the file menu. Upon Clicking 'Preferences' from
'File' Menu, the below dialog opens.
We will go through the most frequently used 'HTTP Settings' in details.
1.Denotes the HTTP Version to be used for
request and response.
2.'User-Agent Header' allows user to can be
predefined using this option. If not defined, it
uses the default http client header.
3.Allows user to specify the compression
method. It can be either gzip or deflate or
None.
4.'If Checked', allows compressed response
from hosts.
5.'If Checked' disables decompression of the
compressed responses.
6.'If Checked' closes HTTP connection for
each SOAP Request.
7.'If Checked', allows user to specify
authentication information for the outgoing
requests.
8.Allows user to restrict the maximum number
of bytes to be read from a response. ZERO
corresponds to unlimited size.

FILE >> PREFERENCES >> WSDL SETTINGS - SoapUI
Now, we will go through the most frequently used 'WSDL Settings' in details.
1.Cache WSDLs Turns on and off caching of
WSDL's
2.Generates example values in requests
3.Allows users to always include optional
elements in generated requests
4.Response messages are printed in the
response editor
5.Allows user to specify a directory containing
schema (.xsd) files while validating WSDL
requests. Upon changing the contents of this
directory SOAP UI requires a restart.
6.For the purpose of preserving space, the
minimum message size to be compressed in the
SoapUI project file.

FILE >> PREFERENCES >> UI SETTINGS - SoapUI
Now, we will go through the most frequently used 'UI Settings' in details.
1.Closes all projects while launching
SOAP UI for better startup-time and
consumes less memory.
2.Displays description whenever
available.
3.Automatically saves all projects while
exiting SOAP UI.
4.Before saving, SOAP UI creates a
backup of the project. If enabled, back
up folder has to be mentioned.
5.Displays and expands the log tabs
upon starting SOAP UI.
6.Displays the 'start up page' dialog
upon starting SOAP UI.
7.Upon disabling tool tip, disables tool
tip when user hovers mouse over the
options/buttons while navigation.

HELP - SoapUI
HELP: Let us take a look at the important Help menu options.

Create Project, Test Suit, Test Cases- SoapUI
Create a Project
Step 1: Now depending upon the project, we need to import SOAP/REST protocol. We
will create a new SOAP Project.

Create a project- SoapUI
Step 2: We will make use following SOAP request
1. Enter the Project Name
2. Enter the path of the WSDL request. In this
case http://www.webservicex.net/CurrencyConvertor.asmx?WSDL
3. Click OK

Step 3: Upon creating the SOAP project with the above-said WSDL, we will be able to see
that there are two operations that will be imported into the project.

Step 4) Expand the first request and double click on the 'Request1'. It will display the
SOAP request in the XML format.

Create a project- - SoapUI
1. Enter the From Currency and To Currency
2. Click on the submit button. Response XML will be displayed right side pane.

Creating a test suit- - SoapUI
Step 1: Within the project, testers can create a test suite by performing a right click on
the root of the project.

Creating a test suit- SoapUI
Step 2: We need to enter the name of the test suite and press OK.
Step 3: The created test suite is displayed the navigator pane as shown below.

Creating a test suit- SoapUI
Step 4: The test Suite window opens in the Right Pane. As we have just created there
are NO test cases. Hence all options are disabled.

Creating Test Case- SoapUI
Creating Test Case
Step 1: Within a test suite, we can create multiple test cases by performing right click on
the 'test suite' and choosing 'New Test Case'.

Creating Test Case- SoapUI
Step 2: Specify the name of the Test Case and click 'OK'.

Creating test case- SoapUI
Step 3: The created test case has zero steps as shown below. (We can see that the test
case is added with zero test steps for all kinds of tests available. Upon adding the test
steps the numbers in the bracket would change automatically. )
The functional test step should go into 'Test Steps' while a performance test step should go
into 'Load Test' and a security test step should go into 'security Tests'.

Creating test step- SoapUI
Step 4: We can insert a variety of test steps by performing a right click on test steps and
selecting an appropriate test step as shown below.
So if you were to test a REST WebService, you would select the REST Test Request.

Test Step Insert
Now let us add a test step to validate the imported SOAP request.
Step 1: Add a new step 'SOAP Test Request' as shown below.
Step 2: Enter the step name and click OK.

Creating test step - SoapUI
Step 3: Upon clicking 'OK', a dialog pops up to select the operation to invoke.
There are two operations that will be listed. Both the Operations are the same except the
SOAP version used.
CurrencyConvertorSoap – uses SOAP version 1.1 where as,
CurrencyConvertorSoap12 – uses SOAP version 1.2
The Version does not matter for us in this context. Hence you can select the one of your
choice.
Upon Selecting the operation, click 'Ok'

Step 4: While adding a test case, we can add standard assertions.
We can add following checkpoints/assertions while creating test case. Let us create a test
case with the default option which means creating test step WITHOUT any of the below
validation points
1. Verifies if the response message is SOAP, upon executing the test.
2. Verifies if the response schema is valid.
3. Verifies if the SOAP response contains FAULT.

Step 5: Upon creating the test case, the request XML is shown below.

Request and Response - SoapUI
Step 6: The test step count is now incremented to one as we have just added one test
step. Similarly upon adding load and security tests step, the corresponding number would
be automatically incremented based on the number of steps added.

Send Request Manually & Reading Response
Step 1: We would like to convert the currency from USD to INR.
FromCurrency – USD
ToCurrency – INR
Next, We need to enter these inputs in place of the question mark which will be sent as
request XML.
After inputting those values into the corresponding XML tags, click 'submit request' button
to check the response.

Step 2: After submitting a request the web service request is processed by the
webserver and sends back a response as shown below.
By reading the response, we are able to conclude that 1 unit of USD = (-1) units of INR.

Soap Response & Log Panels- SoapUI
Understanding the Soap Response & Log Panels
SOAP messages are transported via HTTP protocol. Let us take a look at the RAW
messages.
Step 1: Click 'RAW' Tab in both SOAP-UI request Window.
The Request is posted to the webserver. Hence, the POST method of Http is used.
The SOAP Request is transported in the body of the Http message as shown below

Step 2: Now click 'RAW' Tab in SOAP-UI Response Window to understand how the
response is sent via HTTP.
After processing the request, the Http response code (200) is shown which means it is a
success. The webserver has processed it successfully.
The SOAP response is sent back to the client as part of the body of the HTTP message.

HTTP Status Response Codes - SoapUI
Http Code Description
100 – Continue
101 - Switching Protocols
Informational - This means a request received and continuing
process.
200 -- OK
201 -- Created
202 -- Accepted
203 -- Non-Authoritative Information
204 -- No Content
205 -- Reset Content
206 -- Partial Content
Success - The action was successfully received, understood,
and accepted.
300 -- Multiple Choices
301 -- Moved Permanently
302 -- Found
303 -- See Other
304 -- Not Modified
305 -- Use Proxy
307 -- Temporary Redirect
Redirection - This means further action must be taken in order
to complete the request.
400 -- Bad Request
401 -- Unauthorized
402 -- Payment Required
403 -- Forbidden
404 -- Not Found
Client Error - This means the request contains bad syntax or
cannot be fulfilled
500 -- Internal Server Error
501 -- Not Implemented
502 -- Bad Gateway
503 -- Service Unavailable
504 -- Gateway Timeout - 505 - HTTP Version Not Supported
Server Error - The server failed to fulfill an apparently valid
request
A Quick snapshot of the Http Response codes for easy understanding and debugging.
The below table will help you to trouble shoot based on the HTTP code received from the
webserver.

Step 3: Let us understand the other information that are displayed in the test case window.
1.Represent NO header in the request that is being sent
2.Represents NO attachments in the request that is being sent to the web server.
3.Represents 12 header information and the same are displayed upon clicking on it.
4.Represents that there are no attachments from the response message.

Log Panels- SoapUI
SoapUI Log: has the complete information regarding the transaction between the client and
the server. Users will be able to see the tabs of the Log pane as shown below.

Log Panels- SoapUI
Http log: Displays all the HTTP packet transfer. All the information in 'RAW' is shown in HTTP
log.

Log Panels- SoapUI
Error Log – Error log displays all the errors that we have encountered during the entire project
session. The same information is available in 'soapui-errors.log' present in the 'bin' directory of
the SOAP UI installed location.
Memory Log – This tab monitors the memory consumption and displays it in the form of the
chart as shown below. It is really helpful when there is a memory intensive operation is
performed.
Now that we have created test suite, test case, test step and got a response, next step is
to validate the response.

Assertions - SoapUI
Assertion means act of affirming or stating something. It can also be interpreted as check point
or a validation point.
Once a request is sent to a web server a response is received. We need to validate if the
response contains the data that we expect. In order to validate the response, we need to use
assertions.
Types Of Assertion
There are various ways of asserting a response; however we will focus on the commonly used
Assertions types while validating a response. Below are the ones that are available in Open
Source version of SoapUI.
1. Contains Assertion
2. Not contains Assertion
3. X Path Match Assertion.
4. X Query Match Assertion
5. Scripting Assertion

More learning - SoapUI
The more we practice, the more we learn.
The next session will learn-
1. Functional Testing
2. Load Testing
3. API testing
4. Security Testing.
5. Mock Service
6. Reports

Q & A- - SoapUI

SoapUI

Testing soap UI

More Related Content

What's hot

Similar to Testing soap UI

Recently uploaded

Testing soap UI

Editor's Notes