26 September 2008 - 2.5-beta1 home user guide eclipse intellij netbeans maven PDF files forums bugs sourceforge eviware.com


Eviware Logo

soapUI 2.0 new features!

Welcome to soapUI 2.0! For the big two oh we have lined up a number of features that significantly extends what you can do with soapUI.

As always, make backups of your project files before switching and let us know if you have any issues!

soapUI 2.0.1
soapUI WebStart
[Download]
soapUI 2.0.1 Pro
soapUI Pro WebStart
[Try or buy soapUI Pro] [soapUI FAQ]

The most notable improvements to both soapUI and soapUI Pro are described below, on top of these are a large number of bug fixes, minor UI improvements.

soapUI Movies

In order for you to be able to see some of the more complex functionality in action we have created some simple movies.





Did you know...?

soapUI Pro 2 includes Web Service Coverage. See how well tested your Web Services are!

soapUI Pro contains productivity enhancements as well as offers Professional World Class support.

soapUI 2.0.2 Release

The 2.0.2 release is mainly another bug-fix release with a small number of improvements and also includes updated version of all IDE / maven plugins;

  • Fixed -n option for commandline LoadTestRunner (was incorrectly -h)
  • Fixed internal initialization of copied/cloned testcases/teststeps and during loadtesting
  • Improved Aut/Header inspectors to be visible for form/overview views
  • Fixed quoting of SOAP 1.2 Action in content-type header
  • Improved opening of local files in external browser (reports, etc)
  • Fixed initialization of custom RequestFilters
  • Fixed script-evaluation in MockResponses to allow modification of the responseContent
  • Fixed logging/display of failed MockRequests
  • Fixed caching of external WSDLs in SchemaComplianceAssertion if another URL was used
  • Fixed attribute handling with wildcards
  • Fixed NPE on empty response messages
  • Fixed a number of typos
  • Updated to trunk version of XMLBeans which fixes corruption of project-files on save
  • Updated to full version of xercesImpl 2.9.1 for full JAXP functionality
  • etc..

soapUI Pro-specific updates:

  • Fixed Get Data popup in MockResponse editors
  • Added support for description column when importing/exporting requirements
  • etc..

soapUI 2.0.1 Release

The 2.0.1 release is mainly a bug-fix release but also includes a small number of improvements:

  • Updated Groovy to 1.5.1
  • Fixed Keystore-initialization to use specified provider
  • Fixed NPE when initializing properties
  • Fixed corruption of PropertyTransfer, ConditionalGoto and RunTestCase teststeps
  • Fixed invalid Regular Expression in XSDs to get discarded and show a warning
  • Fixed parallel execution of TestCases in TestSuites
  • Fixed encoding-problems when compiling Groovy Scripts
  • Added support for %20 as space-delimiter in command-line arguments (for Unix/linux)
  • Fixed check to recreate messages when updating interface
  • Fixed global properties as PropertyTransfer targets
  • Fixed NPE:s in related to TestCase and MockService logs
  • Fixed DnD of requests to TestCases
  • Memory fixes
  • etc..

soapUI Pro has the following additional fixes/improvements

  • Fixed generation of indexed XPath expressions
  • Fixed refactoring issues with namespaces and multiple updates
  • Improved WSDL Coverage:
    • Added possibility to exclude elements from coverage calculation
    • Fixed handling of empty elements
    • Moved settings to be at project-level
  • Added option to skip to closing DataSource Loop when no data is available in a DataSource TestStep
  • Improved import/export of requirements to include testcases and links
  • etc..

As always thanks to all of you that have reported issues and helped us track them down!

New and Noteworthy in the soapUI 2 Final Release

Final Fixes

beta2 proved relatively stable so, there were few updates. Fixes were done to

  • Coverage
  • Refactoring
  • LoadTests
  • Security

New and Noteworthy in soapUI 2 beta2



  • Web Service Coverage Updated!

    We have made some major and some minor upgrades to Web Service Coverage, especially concerning Assertion Coverage.

    • Updated Assertions Parsing to be more accurate
    • Performance Updates
    • Coverage now takes disabled TestSteps into consideration
    • Added Message Content Inspector
    • Spiffed up Run Log





  • WSDL Refactoring Updated!

    We have made some very major and some minor upgrades to WSDL Refactoring, making WSDL Refactoring more robust, versatile and usable.





  • Aut Inspector

    For easy access to authentication-related settings this new Inspector provides a form with corresponding fields from the request properties table.





  • WS-Security Remade!

    We weren't pleased with WS-Security in beta 1 and have updated it extensively.

    The following improvements have been made:

    • WS-Security configurations are now managed at the project-level from the WS-Security Tab in the Project Viewer. Here you configure three types of components:
      1. Keystores/Certificates : Keystores, Key-files, certificates, etc... that are used for signing and en/de-cryption.
      2. Incoming WSS configurations : Configurations that can be associated with incoming messages: Request-Responses, Mock-Requests and Monitor-Requests/Responses for decrypting, verification, etc.
      3. Outgoing WSS configurations : Configurations that can be associated with outgoing messages: Requests and MockResponses. These are further assembled from an arbitrary number of entries for encryption, signatures, etc..
    • You then refer to these configurations in the requests and responses either from the new "Aut" inspector which handles all authentication-related settings for a request, or from dedicated Property-editors/fields
    • MockServices can have an associated Incoming WSS configuration that will be used to decrypt any incoming messages before they are dispatched which may be necessary for correct dispatch if the entire message content is encrypted.
    • SOAP Monitors can have associated Incoming WSS configurations for decrypting/verifying both incoming requests to the target service and for the corresponding response, making it easy to see encrypted data, etc..
    • We have also updated significantly the scope of the WS-Security Standard we support; bith Signature and Encryption entries have been extended with a large number of settings related to algorithms, content, tokens, etc...
    • A WSS Assertion has been added to the list of possible response assertions for checking that a response has valid WS-Security content
    • Support for extended UsernameToken password hashing

    Please note that the beta1 WSS-related configurations will be lost and will have to be manually /recreated with the new features, sorry for any inconvenience this may cause.





  • Interface viewer expanded

    The Interface Viewer now sports four tabs.

    1. Overview. A nice overview of the interface, it is an easy way of for example seeing if the interface is Document/Literal.
    2. Service Endpoints. The Service Endpoint Editor was available by right-clicking the interface before but is now in a non-modal tab which we think increases usability. Also, it is now possible to associate default incoming/outgoing WSS configurations (see above) with an endpoint.
    3. WSDL Content. The Old inspector, view the WSDL.
    4. WS-I Compliance. This was, as Service Endpoints, available in the Interface context menu, but is added for usability reasons.





  • TestCase Log spiffed up

    The Interface Viewer now sports four tabs.

    This is no major update, but we realized a lot of users did not know that the log was clickable, so we made all clickable steps blue and underlined to signify clickability.





  • A new read-only "Raw" editor tab has been added to both request and response editors displaying the actual content of the underlying request/response as it was last transmitted over the wire. This can be great help when trying to debug property-transfers/expansions, WS-Security configurations, etc..




  • LoadTests can now continuously export statistics to comma-separated files for manuall processing/reporting in Excel, etc...




  • The message-viewer available for logged messages has been enhanced to show request/response messages with the "standard" message editors, including all inspectors, etc..




  • Minor improvements/additions:

    • Option to not send the SOAP-Action header in outgoing requests for "REST"-like requests
    • TestCase timeout setting (in the TestCase Options dialog) for setting a timeout after which the TestCase fails
    • Request-level pretty-printing via a "Pretty Print" property in the request properties list
    • Option to cancel running TestCases when a LoadTest reaches its limit
    • Updated BouncyCastle to 1.3.8 and not-yet-commons-ssl to 0.3.9 with removed single-key validation
    • etc... etc...

    And of course a bunch of bug-fixes.. Thank you to all who helped us test and improve!!

New and Noteworthy in soapUI beta1



  • WS-Security

    In soapUI 2.0 beta 1 we introduce initial support for Web Service Security. soapUI 2.0 final will have support for the following WS-Security standards;

    • OASIS Web Services Security: SOAP Message Security 1.0 Standard 200401, March 2004
    • Username Token profile V1.0
    • X.509 Token Profile V1.0

    The addition of WS-Security support in soapUI makes it possible for soapUI users to;

    • Sign Web Service Messages
    • Encrypt/Decrypt Web Service Messages
    • Authenticate through the usage of tokens
    • Use SAML Assertion insertion

    Please evaluate and come back with feedback on how we can improve the interface





  • Message Capturing and Recording





    soapUI 2.0 beta 1 contains a SOAP Monitor for capturing live traffic. The SOAP Monitor can be run in both Tunnel and Proxy Modes. From the traffic captured in soapUI SOAP Monitor you can;

    • Create requests
    • Create TestCases
    • Create MockServices

    Launch it by right-clicking a project and choose "soap test Launch SOAP Monitor"





  • Memory Log

    As a complement to the test quality inspectors in soapUI, we now introduce the Memory Log. The Memory Log will enable you to monitor Memory Consumption during tests.





  • Run TestCase TestStep

    We have long looked for a way of building chains of tests where TestCases depend in each other. The solution is here in the form of the Run TestCase TestStep. The Run TestCase TestStep allows parameter input and output.





  • Setup and Teardown scripts

    Any TestSuite or TestCase can now have Setup and Teardown scripts just like Unit tests. These scripts can be used to create time stamps, write test results to a file or even send mail!





  • Disable TestCase

    You can now disable TestCases in order to skip them in TestSuite runs.





  • Disable Assertion

    You can now disable assertions in TestSteps.





  • Disable TestSuite

    You can now disable TestSuites. This will enable you to skip TestSuites in Command Line tests as well in WSDL Coverage analysis(WSDL is Pro only).





  • MockService SSL Support

    soapUI MockServices now supports SSL for Service Mocking of SSL Web Services.





  • MockService WSDL Exposure

    In order to make soapUI Mocking even more like the real thing you are now able to expose the WSDL for all MockServices in soapUI.





  • Mocking Start and Stop Scripts

    You are now able to run scripts at the start or stop of MockServices. This gives you the ability to manipulate properties, context variables or other when you start or stop a MockService.





  • Project Overview

    When you double click a soapUI Project, you now get the soapUI Project Overview. This project overview will show;

    • Project Metrics
    • Load Save Scripts





  • TestSuite Editor run log

    Like TestCases before, TestSuites now sports a log window showing each step run in a TestCase. Double Click any logged event in the TestSuite log to see the actual content of the step.





  • Properties Management

    You are now able to create and use properties on the following levels;

    • Global Properties
    • Project Properties
    • TestSuite Properties
    • TestCase Properties

    Properties can then be used in levels below the property. That mean you are now able to share Properties such as user names and passwords in between for example TestCases.

    PropertyExpansions and PropertyTransfers have been extended accordingly. While the old TestStep properties remain unchanged the syntax of the new properties is extended. They now can refer to properties in other levels in the soapUI hierarchy by explicitly stating which property at which level you are referring to. Properties now have the following Syntax;

    ${#Scope#Property-name[#xpath-expression]}
    					
    ${Property-name} refers to a Global Property (example: ${UserName} to a global Property named "UserName")
    ${#Project#Property-name}refers to a Project Property (example: ${#Project#UserName} to a Property on 
    Project level named "UserName")
    ${#TestSuite#Property-name} refers to a TestSuite Property (example: ${#TestSuite#UserName} to a Property 
    on TestSuite level named "UserName")
    ${#TestCase#Property-name} refers to a TestCase Property (example: ${#TestCase#UserName} to a Property 
    on TestCase level named "UserName")
    ${TestStep-name#Property-name} refers to a property in a named TestStep.
    

    The following rules apply:

    • Excepting TestSteps, you can only refer to properties in a path straight ascending from where you are
    • Only TestSteps are referred to by name
    • if you are running soapUI from command line, Global Properties will be overridden by file based Global Properties (read more about [these here])

    You can drag a Property to an element in a TestRequest in order to create an automatic PropertyExpansion. You can also rename a Property without fear of breaking any tests; references to Properties automatically reactors themselves, rename a property and all PropertyExpansions will rename themselves.





  • Extended Properties view

    You can now have the ability to view properties directly in the tree navigator. This has two advantages

    1. You are able to get better overview of the properties available
    2. You can drag a property from the tree to any Request element for an instant PropertyExpansion
    The Extended Properties View is toggle able.





  • TestCase Log improvements

    1. In the TestCase Log you now can limit output and logged results to preserve memory under long running tests.
    2. You can also generate MockServices from TestCase execution





  • Minor add ons and improvements;
    • You can now start and stop MockServices from the soapUI Navigator by right clicking a MockService
    • Bundled version of soapUI in the soapUI Installer now is JDK 1.6.03
    • etc...

New and Noteworthy in soapUI Pro

On top of all the above, the following improvements/additions have been made to soapUI Pro:



  • Web Service Coverage





    As the first testing tool in the world soapUI releases support for WSDL Coverage analysis. With one simple analysis run you can see how much of the WSDL contract that is covered by your tests, see a coverage report per request and all the way down to which element is tested. This is integrated into the test development process and as you create tests you will see the coverage increase.

    Coverage can be calculated on several levels:

    • Functional Tests - calculate the WSDL coverage for your running tests, how much of the WSDL contract are you actually testing and asserting?
    • MockServices - calculate the WSDL coverage for your MockServices, how much of the WSDL contract are you client sending in and mocks returning?
    • Monitors - calculate the WSDL coverage on monitored traffic, how much of your WSDL contract are you actually using?

    Coverage information is updated in realtime and can be ongoing monitored during the above mentioned processes

    Also, a specialized Coverage Inspector is available for displaying an edited messages coverage:

    soap test specialiaed coverage inspector

    This exclusive functionality will increase development quality, speed and make the Web Service testing faster than ever before.





  • WSDL Refactoring





    WSDL Refactoring enables you to refactor all your tests as the WSDL is updated. Run "Refactor Definition" on your interface in order to update your tests. WSDL Refactoring will take into account how the updated WSDL affects your XPath expressions. WSDL Refactoring will save you man hours upon man hours and will enable you to focus on writing tests, not updating them. This makes soapUI a perfect tool for Agile Web Service Testing.





  • Requirements

    In soapUI 2.0 we introduce an efficient way of managing requirements and connecting these to the tests in soapUI. Create or import requirements, choose which TestCases meets which requirements and see requirement fulfillment. soapUI Requirements is a welcome addition for the professional user, providing the opportunity to integrate your testing tool in the requirements management process.





  • DataSink TestStep

    In soapUI Pro you have earlier been able to get data for your functional testing by the DataSource TestStep, but not been able to put data from your test in a database. soapUI Pro 2.0 introduces the DataSink TestStep which enables you to put data from you?re your TestResponses in a database, Excel file or csv-file.





  • Many minor add ons and improvements;
    • Overview View now shows SOAP Headers
    • JDBC DataSource now supports Stored Procedures
    • etc...