SoapUI Feature Requests

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

Outline:  The Project's properties are not visible (or initialised) before project "Load script" is executed.   Actual Behaviour Given a new Project with a Name and Description. When the following code in added to Project's 'Load Script' // Sanity check that script is actually run log.info Runtime.class.getPackage().getSpecificationVersion(); // ... and the the script is actually expected project. log.info project.getClass().getName() // These properties should be defined already. log.info project.getProperties() log.info project.getProperty("Name") log.info project.getPropertyValue("Name") log.info project.getPropertyValue("Description") Then the script log shows the following Tue Apr 02 09:51:29 BST 2019:INFO:1.8 Tue Apr 02 09:51:29 BST 2019:INFO:1.8.0_181 Tue Apr 02 09:51:29 BST 2019:INFO:com.eviware.soapui.impl.wsdl.WsdlProject Tue Apr 02 09:51:29 BST 2019:INFO:{} Tue Apr 02 09:51:29 BST 2019:INFO:null Tue Apr 02 09:51:29 BST 2019:INFO:null Tue Apr 02 09:51:29 BST 2019:INFO:null Expected behaviour The log should include the values shown to befined in screenshot.   Inference The Project's 'Load Script' is being run before the project is fully loaded/initialised.   ... View more

Dear all, I have a SoapUI project and am not able to add a WSDL in the following circumstances.   Problem description I have a SoapUI project (in SoapUI version 5.4.0): one of the WSDL interfaces is called "bindingServiceName". I have a completely different WSDL/service, which contains a binding with the same name " bindingServiceName " and which I need to import to the project as well.   When I try to add the second WSDL to SoapUI project I get a dialogue: Interface [ bindingServiceName ] already exists in project, update instead? Yes No Cancel   Apparently "Yes" is not an option as these services are completely different and I need them both. When I choose "No", no interface is added to the project.   It seems this is an old issue, known in 2009 already.    Proposal I suggest that in such a situation SoapUI would: warn that the WSDL contains the same binding name as already exists within the project and offer an input to get a different (unique) name for the imported binding I would be helpful if this gets resolved. Currently, we need to do an unpleasant workaround.   ... View more

This file is missing in the SmartBear maven repository http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-project/5.4.0/soapui-project-5.4.0.pom   It is referenced from http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui/5.4.0/soapui-5.4.0.pom   Can someone please publish it? ... View more

It would be very convenient to work with several windows if they were organized as tabs, as in modern browsers. Now, to quickly switch between windows, you have to reduce their size and change the position of each other so that one window looks out from under the other. See attached screenshot. ... View more

Since it is possible to configure multiple endpoints on a soapcall I think it would be a nice feature to  be able to assign a name or description to each endpoint. For instance, in a situation where you can only use IP adresses it would be nice to set the hostname in the description. Another usecase would be a 'production', 'test', 'accept' tag in the description etc.   ... View more

Hi,   Please resolve bug Null pointer exception with HTTP Monitor.   Http Monitor + create test case from selected request would be a very useful feature, but as far as I can see (in version 5.3.0) this is currently completely unusable.   Its working in Pro version, so I guess a fix wouldn't be very difficult to implement?   Kind Regards, Paul Igoe ... View more

Hello,   I've been using the mock functionality and I have a feature request to make.   In Home / Documentation / SOAP Mocking / MockOperations and Responses:   https://www.soapui.org/soap-mocking/mockoperations-and-responses.html   Section MockOperation Dispatching: SEQUENCE: this is the simplest dispatch method; responses are selected and returned in the order they have been added to the MockOperation.   If you are setting up a mock service with a bunch of fake responses and you need to change their order, it can become quite cumbersome since you would need to recreate them or swap their contents around.   I wish there was a better way to reorder the responses, preferable by dragging them, without having to use a QUERY-MATCH MockOperation dispatcher, which would involve more complexity.   cheers ... View more

It would be helpful if a user was able to choose whether or not they wish to have Logs scroll as they populate or not. Each log (Error, HTTP, Script, etc) should have their own setting and not have one setting to rule them all. I have created several scripted assertions with a great bit of detail. I have to wait until the test is finished running before I can describe or research the error I am receiving. This is not very efficient when I have individuals assisting with debugging of an application.   Heather A. ... View more

When making calls to Amazon's S3 and similar services a "signature" value needs to be generated.   http://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html   The details of the signing required are documented here http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html    Currently this can only be accomplished with a convoluted mechanism of groovy scripts.  It would be very useful if (upon entering the relevant credentials) SoapUI could generate the signature value and populate the relevant header.   ... View more

Purpose When the Groovy Script test step fails, its star icon turns red and I can see the step has failed. When the step succeeds, the icon is still blue, i.e. has the same color as before its execution. Can you please make it green in case of test step success, as is e.g. in case of SOAP Request test step?   Description When I run a Groovy script test step with a script:   assert false The icon gets red: However if the script is:   assert true The icon remains blue, i.e. the same as before step execution: It is a small change but it would help to recognize the test result.   Karel   ... View more