Skip to main content

SoapUI - Part 1

Starting from today I want to share part of my knowledge about SoapUI (as promised at the end of the post http://googlielmo.blogspot.ie/2013/12/dance-into-groovy.html). I used this tool for some years in order to perform load testing and integration testing and I found it really helpful.
SoapUI is a tool that allows any kind of functional and not functional testing. Despite its name it is not limited to the SOAP protocol and to web services only: you can perform tests for different protocols (HTTP/S, REST, JDBC, AMF, etc.) and application layers. It was born to be used for SOAP web services testing, but then it evolved to be a general purpose testing tool.
It comes in two editions, Open Source and Pro. The first one is free to use and you can modifiy the source code too, according to the LGPL license. The second one is commercial and closed source. In this post and the following I will refer to the Open Source edition. The companies I worked for in the last years didn't want to buy the Pro licenses even though they were happy with the benefits gained using this product, so my experience of usage against real systems is based mostly on the OS edition. Based on this I can assert that this edition can cover the most significant part of system testing. Furthermore, SoapUI is very flexible and can be extended through scripts, using a language like Groovy.
SoapUI is written in Java, so it is platform independent. The installation is very simple: go to the offiicial website (http://www.soapui.org/) and download the release for your OS. The only prerequisite for this tool is a Java Runtime Environment. You can choose between installer packages incuding a JRE or not (if you prefer to use the one already installed in your system).
SoapUI comes with a really user-friendly User Interface. This way it is easy to quickly create and execute any kind of automated test through a single point of access.

SoapUi user interface
SoapUI user interface


SoapUI provides also other features, like web service mocking, security testing and recording.
The large Open Source community for it accelerated the integration with other popular tools. So you can find plugins for the most popular Java IDEs (Eclipse, NetBeans, IntelliJ) and for other helpful tools for automation (Jenkins, Maven, Ant, etc.).
In the next post we will see the anatomy of a SoapUI project.
Labels:

Comments

Post a Comment

Popular posts from this blog

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do
Post a Comment
Read more

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv
6 comments
Read more

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You
5 comments
Read more