Download code from GitHub
With the increase in implementation of service-oriented architecture (SOA), architecture across applications leads to various technological and business advantages to the organizations implementing it.
But as it's said; There are two sides to every coin, with SOA architecture came advantages such as the following:
Reusability
Better scalability
Platform independency
Business agility
Enhanced security
But there are also disadvantages:
Increased response time
Service management effort is high
Implementation cost is high
In this chapter we will study the following topics:
Introduction to SOA
SoapUI architecture
Test levels in SOA testing
SOA testing approach
Introduction to functional, performance and security testing using SoapUI
Is SOA really advantageous?
Well, let's talk about a few of the advantages of SOA architecture:
Reusability: If we want to reuse the same piece of functionality exposed via a web service we should be absolutely sure that the functionality of the service is working as expected; security of the service is reliable and has no performance bottlenecks.
Business Agility: With more functional changes being easily adopted in a web service, we make the web service prone to functional bugs.
Enhanced Security: Web services are usually wrapped around systems that are being protected by several layers of security like SSL and usage of security tokens. Use of the business layer to protect the technical services to be directly exposed is usually handled by these layers. If the security of these layers is removed, the web service is highly vulnerable. Also the use of XML as a communication protocol opens the service to XML based attacks. So to mitigate risks we have SOA testing, and to help you test SOA architecture we have multiple testing tools on the market for example; SoapUI, SoapUI Pro, HP Service Test, ITKO LISA and SOA Parasoft.
But the most widely used and open source tool in the SOA testing arena is SoapUI. Following is a comparative analysis of the most famous tools in the Web service testing & test automation arena.
Comparative Analysis:
|
S.No |
Factors |
SoapUI |
SaopUI PRO |
ITKO LISA |
SOA Parasoft |
|---|---|---|---|---|---|
|
1 |
Cost |
Open source |
400 $/License |
Highly Costly |
Highly Costly |
|
2 |
Multilayer testing |
Yes |
Yes |
Yes |
Yes |
|
3 |
Scripting support |
Yes |
Yes |
Yes |
Yes |
|
4 |
Protocol support |
Yes |
Yes |
Yes |
Yes |
|
5 |
CI support |
Yes |
Yes |
Yes |
Yes |
|
6 |
Ease of use |
8/10 |
9/10 |
9/10 |
9/10 |
|
7 |
Learning curve |
8/10 |
8/10 |
6/10 |
6/10 |
As we can see by the preceding comparison metrics, Ease of use, Learning curve, and Cost play a major role in selection of a tool for any project. So to learn ITKO LISA or SOA Parasoft, there is very limited, or no, material available on the Internet. To get resources trained you need to go to the owners of these tools and pay extra and then pay more if you need the training a second time.
This gives additional advantages to SoapUI and SoapUI Pro to be the first choice for Test Architects and Test Managers for their projects.
Now let's talk about the closely related brothers in this subset; SoapUI & SoapUI Pro are from the same family, Eviware, which is now SmartBear. However, SoapUI Pro has an enriched functionality and GUI which have additional functionalities to help reduce the time for testing, justifying its cost as compared to SoapUI open source.
Here is a quick comparison:
|
Criteria |
SoapUI |
SoapUI Pro |
|---|---|---|
|
Reporting |
Very limited, no rich reporting |
Reports are available in different formats |
|
XPath Builder |
Not Available |
Available |
|
Data source |
Not Available |
Multiple options for data sources available |
|
Data sink |
Not Available |
Available |
|
XQuery Builder |
Not Available |
Available |
The additional functionality that is available in SoapUI Pro can be achieved by SoapUI using Groovy script. To sum up everything that is given as UI functionality in SoapUI PRO is achievable with little effort in SoapUI which finally makes SoapUI open source the preferred choice for tool pickers.
Before we move onto the architecture let's take a look the capabilities of SoapUI and how can we use it for the benefit of our projects.
SoapUI provides the following testing features to the test team:
Functional testing [manual]
Function test automation
Performance testing
Security testing
Web service interoperability testing
Apart from these, SoapUI is also capable of integration with the following:
LoadUI for advanced performance testing
Selenium for multilayer testing
Jenkins for continuous integration
HP QC for end-to-end test automation management and execution
Note
SoapUI has a comparatively simple architecture as compared to other tools in the SOA testing world.
The following image, shows the architecture of SoapUI at an overview level:
Let's talk about the architecture in detail:
Test config files: Files which require power to test this includes test data, expected results, database connection variables and any other environmental or test specific details.
Third-party API: Third-party API helps create an optimized test automation framework example. JExcel API to help integrate with Microsoft Excel to create a data driven framework.
SoapUI Runner: This is used to run the SoapUI project and is a very useful utility for test automation as it allows you to run the test from the command line and acts as a trigger for test automation.
Groovy: This library is used to enable SoapUI to provide its users with groovy as a scripting language.
Properties: Test request properties to hold any dynamically generated data. We also have Test properties to configure SSL and other security configurations for test requests.
Test Report: SoapUI provides a Junit style report and user Jasper reporting utility for reporting of test results.
SoapUI Architecture is composed of many key components which help provide the users of SoapUI with advanced functionality like virtualization, XPath, invoking services with JMS endpoints, logging, and debugging.
Let's discuss these key components in detail:
Jetty: Service virtualization/mock services
We can create replicas of services in cases where the service is not ready or buggy to test. In the meantime, we want to create our test cases, for that we can use service virtualization or mocking and use that service.
Jetty is used for hosting virtual services.
Provided by Eclipse, Java based web server.
Works for both SOAP and Rest.
Jasper:
Saxon XSLT and XQuery processor:
Log4J:
JDBC driver:
Hermes MS:
Scripting language:
Monitoring:
Runners:
Approaches to test SOA architecture are usually based on the scope of the project and requirements to test. Let's look at an example.
Following is a diagram of a three-tier architecture based on SOA architecture:
Validation1 or V1: Validation of integration between Presentation Layer to the Services Layer
Validation2 or V2: Validation of integration between Services Layer to the Service Catalogue Layer
Validation3 or V3: Validation of integration between Product catalogue layer and the database or backend Layer
So we have three integration points which makes us understand that we need integration testing also with functional, performance and security testing. So let's sum up the types of testing that are required to test end-to-end Greenfield projects.
Functional testing
Integration testing
Performance testing
Security testing
Automation testing
A web service may expose single or multiple functionalities via operations and sometimes we need to test a business flow which requires calling multiple services in sequence which is known as orchestration testing in which we validate that a particular business flow meets the requirement.
Click on File in upper-left corner of the top navigation bar.
Click on New SOAP Project heading in the File menu.
Verify that a popup opens up which asks for the WSDL or WADL details. There are two ways you can pass a URL to the web location of the WSDL, or you can pass a link to the downloaded WSDL on your local system.
Enter the project name details and the WSDL location which can either be on your local machine or be called from a URL, then click on OK. You may verify that the WSDL is successfully loaded in SoapUI with all the operations.
Now you can see that service is successfully loaded in the workspace of SoapUI.
Now, the first step toward an organized test suite is to create a test suite and relevant test cases. To achieve this, click on the operation request:
When you click on Add to TestCase you are asked for the test suite name and then a test case name and finally you will be presented with the following popup:
Here you can create a TestCase and add validations to it at run time.
After clicking OK you are ready to start your functional and integration testing:
Let's take an example of how to test a simple web service functionally.
Test case: Validate that Search Customer searches for the customer from the system database using an MSISDN (Telecom Service).
Note
Please note MSISDN is a unique identifier for a user to be searched in the database and is a mandatory parameter.
API to be tested, Search Customer:
Request body:
<v11:SearchCustomerRequest> <v11:username>TEST_Agent1</v11:username> <v11:orgID>COM01</v11:orgID> <v11:MSISDN>447830735969</v11:MSISDN>
So to test it we pass the mandatory parameters and verify the response which should get us the response parameters expected to be fetched.
By this we validate that searching for the customer using some Search criteria is successful or not, similarly, in order to test this service from a business point of view we need to validate this service with multiple scenarios. Following is a list of a few of them.
Considering it's a telecom application search customer service:
Verify that a prepay customer is successfully searched for using Search customer
Verify that a post-pay customer is successfully searched for using Search customer
Verify that agents are successfully searched for using search customer
Verify that the results retrieved in response have the right data
Verify that all the mandatory parameters are presenting the response of the service
Here is how the response looks:
Response Search Customer
<TBD>
Previous are some examples of Priority1 scenarios that you will require to test this service we will give it a deeper look in the following chapters.
So is it really possible to perform performance testing in SoapUI?
The answer is yes, if you just want to do a very simple test on your service itself, not on the orchestration.
SoapUI does have limitations when it comes to performance testing but it does provide you a functionality to generate load on your web service with different strategies.
So to start with, once you have created your SoapUI project for a service operation, you can just convert the same to a simple load test. Here is how:
Right-click on the Load Test option available:
Now select the name of the load test; a more relevant one will help you in future runs.
You will now see that the load test popup appears and the load test is created:
There are several strategies to generate load in SoapUI. The strategies are as follows:
Simple
Burst
Thread
Variance
We will learn more about performance testing using SoapUI in the following chapters.
API and web services are highly vulnerable to security attacks and we need to be absolutely sure about the security of the exposed web service depending on the architecture of the web service and the nature of its use.
Some of the common attacks types include the following:
Boundary attack
Cross-site scripting
XPath injection
SQL injection
Malformed XML
XML bomb
Malicious attachment
SoapUI's security testing functionality provides scans for every attack type and also, if you want to try a custom attack on the service by writing a custom script.
So the scans provided by SoapUI are as follows:
Boundary scan
Cross-site scripting scan
XPath injection scan
SQL injection scan
Malformed XML scan
XML bomb scan
Malicious attachment scan
Fuzzing scan
Custom script
Following are the steps for how we configure a security test in SoapUI:
You can see an option for Security Tests just below
Load Testsin SoapUI.
To add a test, right-click on the Security Tests and select New SecurityTest:
Now select New SecurityTest and verify that a popup asking the name of the security test opens:
Select the name of the security test and click on OK.
After that, you should see the security test configuration window opened on the screen. For the service operation of your test case, in case of multiple operation in the same test case, you can configure for multiple operations in a single security test as well.
For this pane you can select and configure scans on your service operations.
To add a scan, click on the selected icon in the following screenshot:
After selecting the icon, you can now select the scan you want to generate on your operation:
After that you can configure your scan for the relevant parameter by configuring the XPath of the parameter in the request.
After that you can select Assertions and Strategy tabs from the below options:
You are now ready to run you security test with Boundary Scan:
Now we have learnt how to configure a simple security test in SoapUI, we will learn more about it in detail in the coming chapters.
So now we have been introduced to the key features of SoapUI and by the end of this chapter the readers of this chapter will now be familiar with SOA and SOA Testing. They now will have basic understanding of functional, load, and security testing in SOA using SoapUI.
In the following chapter we will be learning about how to test web services and web service orchestration in detail with real-time examples
