Googlielmo's blog

SoapUI can be used as well for automated testing purposes. All the test suites developed through this tool can be executed any way without its user interface, for example using an automated build tool. The SoapUI test cases can be triggered from a command prompt in several ways: a batch file, a shell script, Maven, etc. This post will focus on Apache Maven ( http://maven.apache.org/ ). I will refer to the release 3.1.1. I suggest the readers to have the basics of Maven and Jenkins ( http://jenkins-ci.org/ ) for a better understanding of this post. First of all create the pom.xml file for your Maven project. Add the Maven repository from which to download the soapui plugin: <pluginRepositories>         <pluginRepository>             <id>eviwarePluginRepository</id>             <url>http://www.soapui.org/repository/maven2/</url> ...

In this second part you will discover how to prepare tests for SOAP Web Services using SoapUI. For a better understanding of this post you have to know the basics of SOAP WS. As stated in part 1 ( http://googlielmo.blogspot.com/2013/12/soapui-part-1.html ), I am always referring to the Open Source edition of SoapUI. First of all let's have a quick look at the User Interface. On the upper left part of the UI you can find the project navigator (1). It contains a tree structure of the projects in the workspace. Selecting an item in the navigator you can see its general properties on the bottom left part (2). The central area (3) is the main working area. At the bottom of it there's the logging area (4) containing different tabs, one for each log scope (general SoapUI, Jetty, http requests and responses, errors, memory consumption, etc.). SoapUi uses log4j (http://logging.apache.org/log4j/1.2/ ) for logging, so if you need to customize the log settings you can edit the $SOAP...

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 ...

Groovy ( http://groovy.codehaus.org/ ) is an Object Oriented scripting language for the Java platform. It is dinamically compiled to bytecode for the Java Virtual Machine. It can use and interoperate with any Java class and library (any, not only the ones provided by the JDK) and it has a Java-like syntax: this way its learning curve for a Java depeloper is almost close to zero. Groovy is very powerful and can help in different areas: in some future post I will show and explain better its benefits. In this one I want to show you just a concrete example of use from me in the past. Many times we had to deal with the move of hundreds of Oracle schemas from an envirnoment to another (dev, test, QA, production) or to migrate them from an Oracle release to another. Every time the DBAs regularly forgot to set up the DB links for the new environment. This generated errors that couldn't often be identified quickly. In order to avoid this I wrote a set of Groovy scripts to check the sanity o...