Skip to main content

Testing WEB Sevices and Automating SOAP Services


Web Services are server and client applications to interact with rest of the world over HTTP, or sometimes over SMTP. It is written for accepting requests and giving appropriate answers for each requests. It is assumed that it returns the same response if there is no changing in the request and the condition. Therefore testing and automating Web Services are very easy. You just need to know sending and receiving data and condition, then the rest of the jobs is playing with data and assertions. Information about the Web Services should be present in Web Services documentations and it should be understandable to the people from third party system. 

Web applications take to the next step with the Web Services because you can open your system to rest of world without requiring language specific restrictions. This makes integrity of applications very easy. To be able to integrate two or more system, you just know that you are sending some data and receiving data. 

I had a task for testing Web Services which was written as SOAP.  In this post I want to explain my approach for automating test cases against to Web Services. Example is applied to SOAP services but you can also apply the framework for REST APIs.

What is SOAP

SOAP stands for Simple Object Access Protocol. It is a standard web services access protocol which was developed by Microsoft in 1998. It was developed for replacing older technologies Distributed Component Object Model (DCOM) and Common Object Request Broker Architecture (CORBA). SOAP uses XML (stands for Extensible Markup Language) format for sending and receiving requests. This makes the using SOAP complicated since you need to build requests manually for some languages. SOAP has a good supports for Java and .NET but it is problematic for Python and PHP, for more information click here.SOAP message is a standard XML but it has also the following elements:

  • SOAP ENVELOP: Root element of SOAP messages, everything goes inside of the Envelop. It has two parts: Header and Body. 
  • SOAP HEADER: Header is an optional element. It is composed of any optional attributes which are needed to proceed requests.
  • SOAP BODY: Body is mandatory element. It is composed of informations being sent and receiving informations from the requests.
  • SOAP FAULT: Body is optional element. It contains fault information if there is any fault while processing the requests.

Testing SOAP SERVICES

Even SOAP is a old technology when we compare to REST model, it is still using most of the company especially .Net developer. The good part of SOAP, you can easily get good information about services with WSDL. You can use this link to check the methods and requested url. If you have search for testing SOAP services, most of the time you would have seen lots of links for using SOAPUI or some other tools like SOAPSonar, Web Services Studio, STORM, or add-on for browser as SOA Client. You can see a good list from this link. However there are lots of tools on the market, it is not that easy to test SOAP similar to developing for it. Most of the time 'tool is fool', you have to deal with it is learning curve and have to be contented with the features that tool can give you. 

I used Python requests library to test the SOAP services. What I did is just creating a form variable within a triple-double quotes for Python docstring, like
"""this is triple-double quotes with V1: %s and V2: %s""" %(variable-1, variable-2)
At the end I am just calling requests.post method with sending url, headers, data,and other options. Check the following example: 

Popular posts for software testing and automation

Selenium Error "Element is not currently interactable and may not be manipulated"

Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

Change Default Timeout and Wait Time of Capybara

One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

Page-Object Pattern for Selenium Test Automation with Python

Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to asserting your test cases against to the

Create an Alias for Interactive Console Work: Selenium and Capybara

If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Performance Testing on CI: Locust is running on Jenkins

For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there should be so