SoapUI Feature Requests

When I tried using the Launch Test runner option from ReadyAPI 3.10.2 with below error.   Tue May 17 07:44:33 BST 2022: ERROR: java.lang.NullPointerException: Cannot invoke "com.eviware.soapui.impl.wsdl.tags.Tag.toString()" because the return value of "java.util.Map.get(Object)" is null Tue May 17 07:44:33 BST 2022: ERROR: java.lang.NullPointerException: Cannot invoke "com.eviware.soapui.impl.wsdl.tags.Tag.toString()" because the return value of "java.util.Map.get(Object)" is null java.lang.NullPointerException: Cannot invoke "com.eviware.soapui.impl.wsdl.tags.Tag.toString()" because the return value of "java.util.Map.get(Object)" is null at com.eviware.soapui.impl.wsdl.WsdlProject.getTagById(WsdlProject.java:3186) at com.eviware.soapui.impl.wsdl.actions.iface.tools.soapui.TestRunnerAction.a(TestRunnerAction.java:359) at com.eviware.soapui.impl.wsdl.actions.iface.tools.soapui.TestRunnerAction.refreshTagList(TestRunnerAction.java:309) at com.eviware.soapui.impl.wsdl.actions.iface.tools.soapui.TestRunnerAction.initValues(TestRunnerAction.java:497) at com.eviware.soapui.impl.wsdl.actions.iface.tools.soapui.TestRunnerAction.initValues(TestRunnerAction.java:1) at com.eviware.soapui.impl.wsdl.actions.iface.tools.support.AbstractToolsAction.perform(AbstractToolsAction.java:123) at com.eviware.soapui.impl.wsdl.actions.iface.tools.soapui.ProTestRunnerUIAction.perform(ProTestRunnerUIAction.java:16) at com.eviware.soapui.impl.wsdl.actions.iface.tools.soapui.ProTestRunnerUIAction.perform(ProTestRunnerUIAction.java:1) at com.eviware.soapui.support.action.swing.SwingActionDelegate.actionPerformed(SwingActionDelegate.java:195) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1972) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2313)   ... View more

Dark theme when? ... View more

Hello guys, i try to use the option 'OAuth2'(type 'Resource Owner Password Credentials Grant') and somehow causes 'Failed to retrieve access token. See logs for details...' the logs are  no more detailed ' Wed Apr 13 12:20:55 EEST 2022: ERROR: An error occurred [org.apache.oltu.oauth2.common.exception.OAuthSystemException: OAuthProblemException{error='invalid_request', description='Missing parameters: access_token', uri='null', state='null', scope='null', redirectUri='null', responseStatus=0, parameters={}}], see error log for details' If a set the request for access token in separate request it is up and running, as an embed Auth Profile it meets this error. If someone already met such trouble and have a solution?  ' ... View more

Getting 415 Unsupported Media Type on calling a API for token generation.  I am passing User ID, Password as Headers. The same is working on Postman. Issue observed only on SoapUI ... View more

Hi, Can SOAPUI Open Source be updated to work with Hermes JMS again? I have used this with many clients that I have worked with when doing automated tests for IBM App Connect Enterprise where SOAPUI is writing to and reading from IMB MQ Queues.  I recently tried to get it working with 5.6.1 but after a full day of trying, it didnt work and therefore I've had to revert back to 5.5.0 ... View more

Most of the APIs are now secured by SSL/TLS. Development or test servers sometimes use self-signed certificates or certificates which do not match the server's DNS name.   When I try to connect to such server with SoapUI I get an error, which is fine, but I have no way to go on with the tests.   I woud appreciate having in SoapUI SSL preferences a new option "Do not check certificate", which I could switch on or off.   Some other HTTP tools have an option to ignore server's SSL certificate issues: wget:   --no-check-certificate option curl: -k or --insecure option   Best regards, Karel ... View more

can I export "json" swagger with full response from "Soapui"? the swagger exported contains just response status code, not details. my swagger output: { "swagger" : "2.0" , "info" :{ "version" : "1.0" , "title" : "http://localhost:54480" }, "basePath" : "http://localhost:54480/CustomerImage.svc/GetCustomerPicture/?IdentityNumber=123&AccountNumber=123" , "paths" :{ "/CustomerImage.svc/GetCustomerPicture" :{ "get" :{ "operationId" : "CustomerImage.svc" , "parameters" :[{ "name" : "IdentityNumber" , "in" : "query" , "required" : false , "type" : "string" },{ "name" : "AccountNumber" , "in" : "query" , "required" : false , "type" : "string" }], "responses" :{ "0" :{}, "404" :{}, "200" :{}, "500" :{}}}}} ... View more

SoapUI gives a window for each opened entity (testcase, teststep, request, etc.) and this is good. Only if you have more than 10 windows open, it is really annoying to switch between windows and find the window you want.   Instead, it could work with a tab view (one window with a tab for every open window): at the top of the window, a title for each tab (previously: each window) and the option to close this tab (a small cross button). No maximize or minimize buttons, maximized as standard view of the window. Working with tabs is much more organized than lots of windows which you can't get an overview of. By dragging a tab outside the top line with tabs, the tab is moved to a smaller window without tabs (the window-view currently in production).  ... View more

Request could have the option to generate CURL. ... View more

I have a degenerative eye disability caused by Usher Syndrome which is now turning impossible to work with dark text on white background. Whilst I use a Mircrosoft Windows accessibility feature called High Contrast it doesn't change SoapUI. If Smartbear can't create its own dark-mode for SoapUI, at least, could let Windows turn it to high contrast. Any help, be it any of the 2 features requested or a suggestion, is much welcome.  ... View more

It would be great if there were an option to change logging tabs from the bottom to the right side of the gui.   Sometimes I'm monitoring properties and steps in a test, and I'd like to see the script log specifically on the right. This way we have more control over the screen real estate.   Currently if you want to view both, you have to sacrifice space for script logs, or observing teststeps, or properties. ... View more

I would like to suggest that several rows (instead of just one row) is used for showing the Endpoint, Resource and Parameters which would make viewing a test a little less awkward. Also I notice that trying to amend parameters seems a little clunky, clicking into the fields seems not to be reliable to amend an existing parameter and when the parameter edit window opens it doesn't permit resizing which makes viewing the parameters a little awkward. ... View more

Currently (this is SoapUI 5.5.0) when we create a new GET type REST project with a long URL, this is correctly separated into the fields Endpoint, Resource, Parameters. However, when the resource is a long one, this is unceremoniously and without warning dropped when sending the request to the server! Of course the server usually responds with an error of some kind, like a http 500. This makes for some headaches and hair-pulling the first few times one encounteres this behaviour. You at some point notice that the raw request is missing the resource section, but that realization may take some time. Of course the work-around is to move the resource part to the Endpoint, but really, it's not becoming for a respected product like SoapUI to behave like that. The feature request is therefore to always use the information in the resource field when consuming a REST type web service.   ... View more

As many of us aware that Software development to moving towards API development for the services using Swagger.   Open API Specification 3.0 was out quite some time ago and even service packs available.   However, there is lack of tooling(free) support for the same in the market such as Postman including SmartBear's SoapUI Open Source as well. Not sure about ReadyAPI though. Of course, swagger tools be used to hit the service, but can't be used for the automation.   Latest version of SoapUI OS supports only Swagger 2.0 and it has some limitations (refer here)   So, here the request to SmartBear team is to find when can OAS 3.0 be supported in SoapUI OS. ... View more

Getting error as : This driver is not configured for integrated authentication.      Everything is in place,  the sqljdbc42.jar in C:\Program Files\SmartBear\ReadyAPI-2.8.0\bin\ext path    But still its throwing that error. ... View more

Before I get into details, I'd like to first present the business case for this idea:   I am implementing a new deployment/test pipeline that uses the ready-api-maven-plugin to execute SoapUI tests after our webapps have been deployed inside a Docker container. There are 2 test suites that I would like to execute: One that checks all of the reports in our application, and another that just checks that a filter component is working correctly. The ready-api-maven-plugin has a <testSuite> property, but you can only provide a single test suite -- meaning my only options to execute both of my desired test suites is to: Perform 2 Maven builds, one running each test suite Make a new 'Smoke Test' test suite combining all of the test cases from each suite   Solution 1 adds a ton of overhead -- because I am using a container, it would have to startup a container, execute one test suite, teardown the container, then do the same thing for my 2nd test suite.   Solution 2 is a bit better, but would make managing the test suite a bit cumbersome and redundant -- Between my 2 test suites there are about 30 test cases -- I would have to manually, one-by-one, add all 30 of those test cases as 'Run test case' steps to this new test suite. In addition, by doing this, I lose a bit of granularity in the JUnit reports that are generated because now tests from my reports and filter suites are all grouped into one generic 'Smoke-Test' suite. One of the advantages of reporting on a test-suite level is that I can see at a glance if my reporting or filter is broken by just seeing if that test suite passed or failed.   I see 3 potential solutions:   1) A new 'Test Collection' option which would allow us to create a collection of tests while preserving the test suite they belong to. I think this would be the most complex to implement but would provide a lot of value. This is similar to just adding all of the desired test cases into one test suite, but would be easier to manage because you wouldn't need to add every test case one-by-one, and would (hopefully) still be able to see results on a test-suite level in your JUnit reports. I think the ready-api-maven-plugin would also need to be updated to add a new collection property. Below is an example:   // Test suite/case structure Reports R1 R2 R3 R4 R5 Filter F1 F2 F3 Validation V1 V2 V3 V4 V5 V6 V7 V8 // New test collection Collection 1 Reports R1 R3 R4 Filter F2 Validation V1 V2 V3   2) Add a new 'Run TestSuite' test step -- identical to the 'Run TestCase' step but will execute all of the test cases within that suite   3) Allow for multiple test suites to be specified in the <testSuite> property of the ready-api-maven-plugin and execute them in the order they are specified -- obviously for this to work, you would have to leave <testCase> empty.       ... View more

In SoapUI version 5.5.0, JsonPath library version is 0.9.1. This version was released in 2013. Since, work have been done and the latest version is 2.4.0 (released in 2017).   Would it be possible to update JsonPath library version ? It has be done in ReadyApi and it give user more freedom in assertion. As a reference, you can read jsonpath reference SoapUIPro documentation.     ... View more

When copying the test steps from the test runner the paste buffer contains the object references not the labels. com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep@2a804b01 com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep@56573528 com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep@54e712b8   When copying the test steps from the navigator with (ctrl+c) the paste buffer contains the correct text.             Results in the following useful content for transfer to documentation. Create admin Test Steps (3) Given json content for the create admin request When /admins is Created Then the response is as expected ... View more

Given the following interface   When the Generate TestSuite menu option is used Then the Request are numbered with sequence numbers.   However the  request will actually be unique if the HTTP method is used for the label and clarity would be enhance with multiple of single requests. e.g.     ... View more