Skip to main content

SoapUI Open Source 5.5 Improvements 12th February 2019

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


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.

Download:


Features:

SoapUI Pro

SOAP API Testing
REST API Testing
WSDL Coverage
Scripted Assertions
Largest Online API Testing Community
GraphQL API Testing
Data Generator
Pre-Built Test Assertion Options
End-to-End Testing Support
Multiple Environment Support
CI/CD Automation Support
Customized Reporting Options
SDLC Integrations
Phone and 24-Hour Email Support

SoapUI Open Source

SOAP API Testing
REST API Testing
WSDL Coverage
Scripted Assertions
Largest Online API Testing Community

Source:
SoapUI

Labels:

Comments

Post a Comment

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.
Post a Comment
Read more

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...
Post a Comment
Read more

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...
Post a Comment
Read more