SoapUI Release History

SoapUI's Background

The first version of SoapUI was released in October 2005. The guy behind it was Ole Lensmar, at that time working as the architect of a huge SOA project. “There was simply no test tool available that worked well with an agile development process.” says Ole. “So I had to develop one myself.” For several months Ole worked with the SOA project during the days and developed SoapUI in his spare time. When Ole saw what SoapUI could do for him and his colleagues he decided to share SoapUI with other people working with SOA development and the Open Source version of SoapUI was released.

Since then several releases have been made and today SoapUI is the most used tool for SOA testing in the world. Already from start the ambition was to create a best-in-breed test tool for Web Services and that mission has been a guiding star ever since. Our development strategy rests on two fundamental pillars; humble listening and innovative thinking. We have a close and open relation with our users and listen carefully to their feed-back and suggestions. But we do more than so, often we take the lead and develop brand new solutions actually changing our user’s way of working. What’s in our releases comes from your heads and from our heads; it’s as simple as that.


SoapUI Open Source 5.6.1

Released 20th December 2021

This release updates the Apache Log4j library to v. 2.16 that mitigates CVE-2021-44228 (Log4Shell) and CVE-2021-45046.


SoapUI Open Source 5.6

Released 14th July 2020

Overall Improvements

  • Support for openJDK 12.
  • Updated third-party libraries (org.apache.httpcomponents, commons-logging, commons-codec, and junit).
  • Removed unused third-party libraries (Jackson, KeenIO).
  • The ability of SoapUI to load plugins that are not signed by SmartBear.
  • Better security. SoapUI now disables the Load and Save project scripts by default.

Bug Fixes

  • Now plugins are loaded once during SoapUI launch. Previously they were loaded twice.

SoapUI Open Source 5.5

Released 12th February 2019

Overall Improvements

  • SoapUI 5.5 introduces the Endpoint Explorer dialog. Use it to send exploratory requests and analyze responses without creating a project.
  • SoapUI now supports extended HTTP methods: PROPFIND, LOCK, UNLOCK, COPY, PURGE.
  • Now, if you try to open a project created in a later SoapUI version or in ReadyAPI, SoapUI will notify you about this.
  • SoapUI now requires Java 8 update 112 or higher.

Bug Fixes

  • An invalid name was set for a custom test step.
  • A bug fix by modax: WS-Security did not support Strict Layout Rules.
  • A bug fix by xgcssch: When a refresh token was used to update an OAuth 2.0 access token, the refresh token was not updated.
  • A bug fix by arykov: Symlinks to soapui.sh did not work.

SoapUI Open Source 5.4

Released 27th November 2017

Overall Improvements

  • SoapUI 5.4 uses Apache Commons Collections library version 3.2.2 that fixes a security vulnerability.
  • SoapUI now uses Java 1.8.

  • An improvement by DonnyDepp: The window borders are now thicker, so it is easier to resize windows by dragging their borders.

Bug Fixes

  • A bug fix by vimil: When a response returned redirect status codes, SoapUI always simulated a GET request to the new address. Now, if the initial request uses the POST method, SoapUI simulates a POST request.

Discontinued Support

  • LoadUI integration has been removed from SoapUI. To create and run advanced load tests, use ReadyAPI, which is part of the ReadyAPI application suite.

SoapUI Open Source 5.3

Released 5th December 2016

Major New Features

  1. Integrate your tests with SwaggerHub: SoapUI now has improved integration with SwaggerHub. You can import swagger definitions from SwaggerHub and create tests. 
  2. Enhanced OAuth support: We have improved OAuth and added OAuth 1 support. OAuth 2 support was already available in SoapUI.
  3. Improved support for OAuth 2. SoapUI now supports two additional grant types: Resource Owner Password Credentials and Client Credentials.
  4. A new feature by krzysbaranski: Support for Server Name Indication (SNI) in TLS/SSL requests.
  5. A new feature by BoukeNijhuis: The XQuery Match assertion now supports the "Ignore namespace prefix" and "Ignore XML Comments" options.
  6. A new feature by smithk86: The Set Endpoint dialog now displays endpoints in alphabetical order.
  7. Many thanks to Krzysztof, Bouke and Kyle for their efforts!
  8. The design of some buttons has been updated.
  9. The SoapUI icon on Mac OS X has been updated.

Bundled Plugin

  1. Import your Postman collections: If you have been using Postman to check your API endpoints so far, you can bring your work over to SoapUI by importing your Postman collections.
  2. The Postman plugin is now included in the SoapUI installation package. You use this plugin to import Postman collections and tests to SoapUI. 

Bug Fixes

  1. TestRunner displayed the "Usage statistics" dialog upon starting. To close this dialog, you had to click any button in it, which was inconvenient for automated test runs. 
  2. The JDBC Request test step converted all SQL column names in responses to upper case. This could cause issues when comparing the response contents with baseline data. 
  3. The SLA assertion did not support property expansions.
  4. It was impossible to send requests to a secured web service through a proxy server. The simulated requests did not contain the proxy user credentials. 
  5. The Groovy Script assertion called by the JDBC Request test step always returned an error "null".
  6. The context menu of the XML editor had duplicated "Select All" items. 
  7. The Properties test step failed to load the properties, whose names ended with a backslash (\), from a file.
  8. A NoSuchMethodException exception could occur when creating a project from WSDL.
  9. A bug fix by BoukeNijhuis: In certain cases, the Recently Used tab could disappear from the Assertions dialog.
  10. A bug fix by bearsoftware: The Request URL property of the HTTP Request test step did not allow capital letters. 
  11. A bug fix by kekemonster: Multiple concurrent requests to a mock service could cause the HTTP 500 error.
  12. Many thanks to Bouke Nijhuis, bearsoftware and kekemonster for contribution!

SoapUI 5.2

Released 2015-07-02

Major New Features

  • You can use 4 new JSONPath-based assertions:
  • JsonPath Count - Calculates the number of element occurrences in a JSON response.
  • JsonPath Existence Match - Extracts data from a JSON response and compares it with an expected value.
  • JsonPath Match - Checks if a JSON response contains specific node.
  • JsonPath RegEx Match - Extracts data from a JSON response and verifies it with a regular expression. You can find the new assertions in the Add Assertions dialog, in the Property Content assertion group.
  • You can create new empty projects (in earlier versions, projects had to be based on WSDL or WADL, or URI).
  • Improvements

SoapUI 4.5 - The Big Ears Release

Release date: 2012-03-28

Main features:

  • Test Debugging icon-pro
  • Assertion TestSteps icon-pro
  • Message Content Assertion icon-pro
  • TestOnDemand. Run your tests from the Cloud
  • Multi Environment Support icon-pro
  • Floating Licenses icon-pro

Market feedback:

You spoke and we listened. The Big Ears Release was a release that was solely based on what you, our users, wanted to see in upcoming releases. That results are major features like Test Debugging, Multi Environment Support, and Assertion TestStep while are consistently ranked high in surveys regarding the most valuable features in SoapUI.


SoapUI 4.0 – The Security Release

Release date: 2011-06-14

Main features:

  • Security Test Generatoricon-pro
  • XML Bomb
  • SQL Injection
  • Boundary Scan
  • Invalid Data
  • Malformed XML
  • XPath Injection
  • Malicious attachment
  • Custom script
  • Cross site scripting
  • Fuzzing Scan

Market feedback:

The very much awaited Security Scan release is here. Many users have requested security scans to be added to SoapUI. Adding multiple sets of Security Scans helps you ensure your web services are protected from vulnerabilities.


SoapUI 3.6 – The loadUI Release

Release date: 2010-09-14

Main features:

  • loadUI Integration
  • Web Testing
  • Manual TestStep

SoapUI 3.5 – The Protocol Release

Release date: 2010-03-01

Main features:

  • JMS Testing
  • AMF Testing
  • JDBC Testing
  • Visual Query Builder Feature in ReadyAPI

Market feedback:

Many of the SoapUI users have been waiting for this release. The support of new protocols extends SoapUI to become a complete Functional TestWare.

JMS Support makes it possible to send and receive text and binary messages over JMS. AMF Testing provides support to run tests on flash/flex based RIAs (Rich Internet Applications). JDBC Testing provides support to run tests on database applications. All these features have been heavily requested and are received by the market with pleasure.

The Visual Query Builder provides a graphical tool for building complex Database Queries without deep SQL skills. The market feedback shows that this is an excellent addition.


SoapUI 3.0 – The Reporting Release

Release date: 2009-07-09

Main features:

  • Reporting icon-pro
  • Improved REST
  • Inferred Schemas
  • JavaScript Support

Market feedback:

Reporting makes it possible to generate professional reports in a fast and easy way. This feature is a must in a modern professional Testware.

JavaScript enables scripting in the most common script language. The decision to include support for JavaScript was based on a survey where we asked the community which script language they preferred. JavaScript was the superior winner.


SoapUI 2.5 – The REST Release

Release date: 2008-11-18

Main features:

  • REST Support
  • WS-Addressing
  • HTTP Test
  • Composite Projects Feature in ReadyAPI

Market feedback:

With extensive REST and HTTP support, providing functionality needed for testing of web2.0 applications and REST-based architectures, SoapUI became more complete. This was highly appreciated by the market and the number of users increased significantly.

Using Composite Projects for collaborative work on ReadyAPI projects you can split up projects into multiple files which can be saved and reloaded independently. This feature is a necessity for professional projects with several members.


SoapUI 2.0 – The Coverage Release

Release date: 2007-12-12

Main features:

  • Web Service Coverage Feature in ReadyAPI
  • Team Projects Feature  in ReadyAPI
  • WSDL Refactoring Feature in ReadyAPI
  • WS-Security
  • Requirements Feature in SoapUI  Pro
  • SOAP Monitor

Market feedback:

Some new ReadyAPI specific features were released, each of them giving additional value for our enterprise users.

Web Service Coverage is SoapUI unique, not found in any other testing tool on the market. This feature is a true hit and several users claim that it’s worth buying ReadyAPI just to get it.

Team Projects allows several people to work simultaneously in a project. This instant payback feature was much longed-for since approximately 85% of our users work in project teams.

WSDL Refactoring updates automatically a changed parameter. This can save you days of boring job and you can be sure the parameter is changed wherever it was used.

Requirement Handling provided basic requirement management functionality, highly appreciated by project managers and testers.


SoapUI 1.7.5 – The Community Release

Release date: 2007-09-26

Main features:

More than 75 features requested by the community, e.g.

  • Excel DataSource support for data-driven testing
  • Grid DataSource for managing data-driven test-data from within SoapUI
  • The New Overview Viewer
  • XQuery New Assertion
  • Global Endpoints
  • Command Line Launcher
  • Remote Projects

Market feedback:

This release was dedicated to all our deeply engaged users. To show how much we appreciate them and their input we created a release solely with user originated features. No surprise it became a success!


SoapUI 1.7 – The Pro Release Feature in  ReadyAPI

Release date: 2007-04-10

Main features:

The first ReadyAPI release including:

  • New tree and outline based editor
  • New Form Editor
  • New XML Schema inspector
  • New Table inspector
  • New XML Inspector
  • New Documentation inspector
  • New MockResponse test step for receiving and validating requests within a TestCase.
  • New DataSource and DataSourceLoop TestSteps for easily creating data driven tests from a variety of data sources
  • New alternative Tabbed Desktop for managing editors/windows with docking/dragging support
  • A number of XPath creation wizards where XPath-expressions are required
  • Context sensitive wizards for creating XPath Assertions
  • Context sensitive wizards for easily creating property-transfers to/from request/response messages

Market feedback:

In addition to the Mocking functionality the SoapUI 1.7 release also contained the first version of ReadyAPI, developed as a result of the success the Open Source version had shown to be. As the installed base grew we realized there was a need of a more professional way of handling the SoapUI tool as well as its users. There were a lot of professional users out there with a need of support as well as more advanced functionality. So we took the decision to start a company and to develop the enterprise version ReadyAPI. The Pro version was very well received by the market and it was actually profitable from the first month.


SoapUI 1.7 – The Mock Release

Release date: 2007-04-10

Main features:

  • Mocking of Web Services
  • WSDL Inspection
  • SSL Inspection

Market feedback:

We are proud to say that we pioneered Mock Testing for Web Services and that this release changed the word of testing; in fact it created a paradigm shift. With the Mocking functionality developers could start testing much earlier in the development process and some people were actually using SoapUI not only as a test tool, but also as a development tool. Questions about new developing functionality dropped in and we had to take a decision; either to build a complete development tool or to stick to the test tool. We decided the later; simply because there were a lot of great development tools on the market, but no other really great test tool.


SoapUI 1.6 – The Tools Release

Release date: 2006-11-12

Main features:

  • Code Generation
  • WSDL Generation
  • WS-I Support
  • Apache TCPMon
  • JUnit Reports

Market feedback:

With this release SoapUI strengthened its position as the world’s leading Web Service Testware.

Code Generation integrated all major Web Service frameworks, which made it extremely easy for developers to switch between different frameworks and to compare available features and details of generated code.

WS-I Support made it easy to ensure service and message compliance in integration scenarios. At this point of time no other tool provided this functionality, today it’s a must.

JUnit Reports provided a possibility to generate test reports for assessments. This made SoapUI even more attractive for continuous integration scenarios.


SoapUI 1.5 – The LoadTesting Release

Release date: 2006-04-06

Main features:

  • LoadTesting
  • Improved Functional Testing

Market feedback:

This release was meant as a neat complement to the Initial Release. We were actually a bit surprised when it showed to be the main features for quite a few of our users. The reason why it became so appreciated is that it provides ways to create and modify tests during actual test execution in a very easy way.


SoapUI 1.0 – The Initial Release

Release date: 2005-10-16

Main features:

A complete system aimed for functional testing of Web Services including:

  • Create functional tests of SOAP Web Service
  • Create Test Validations
  • Create Complex Scripts
  • Run Continuous Tests Run Regression Tests

Market feedback:

The response from the market was overwhelming; in the first month more than 5000 downloads were made.


SoapUI 1.5 – The LoadTesting Release

Release date: 2006-04-06

Main features:

  • LoadTesting
  • Improved Functional Testing

Market feedback:

This release was meant as a neat complement to the Initial Release. We were actually a bit surprised when it showed to be the main features for quite a few of our users. The reason why it became so appreciated is that it provides ways to create and modify tests during actual test execution in a very easy way.