Re: Dark Themes
I have a degenerative eye disability caused by Usher Syndrome which is now turning impossible to workwith 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.
Tab view instead of many open windows
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).Resolving "An error occurred [com.eviware.soapui.plugins.auto.factories.AutoDiscoveryMethodFactory]"
Every time I launch SoapUI (5.3.0, but the same was in 5.2.1) I get an error: Thu Jan 26 18:42:52 CET 2017:INFO:Adding plugin from [C:\Users\Karel\.soapuios\plugins\soapui-swagger-plugin-2.2-dist.jar] Thu Jan 26 18:42:53 CET 2017:ERROR:An error occurred [com.eviware.soapui.plugins.auto.factories.AutoImportMethodFactory], see error log for details Can you please resolve this issue and advice a temporary workaround? The plugins actually work, but every time I launch SoapUI (either GUI or programatically) I get an error and need to check whether it's this known error or some other issue with my projects. The only advice I have seen to resolve this is to remove the .soapuios directory, which is actually a workaround, not a solution, as long as we want to use the plugins.Adding Groovy Grape dependency management out-of-the-box
Hi, Groovy Grape dependencies can be a nice alternative for adding Maven repository dependencies at runtime (as an example please see my blog articlehttp://rupertanderson.com/blog/r2-soapui-groovy-grape-dependencies/). To enable Grape dependency management it is necessary to addthe ivy jar to SoapUI's classpath (needs to go in the /lib folder, rather than the usual /bin/ext/), making it a bit less of a standard bolt-on. It could be a nice improvement to add Ivy to the standard SoapUI distribution to enableGroovy Grape dependency management in Groovy TestSteps etc out-of-the-box. I have tested including Ivy 2.4.0 as part of the current 5.2.2 source in GitHub and it appeared to work OK - not that I have everything of course. If other people think this would be a nice feature, please vote for this request and I'll pick it upand submitthe change for approval. Thanks, RupertCompare test step
Purpose The process of testing often requires to compare test results to expected values. When we need to check a specific value, we can use assertions. However, there are often occasions when we need to compare one documents to another (e.g. XML, JSON). I propose to introduce a new type of test step: Compare test step. Functionality Compare test step would allow: Select documents: users would select source and target document from test step requests, responses, properties and other document holders in SoapUI environment, similarly as the Property Transfer test step does. Type of comparisson: the user could choose whether the documents have to be identical (both structure and values) or similar (only the structure should be same). Also the user could choose to ignore differences in whitespaces, attributes, or namespaces, or even data types which to ignore (e.g. xsd:dateTime is typically different). List of items to compare/ignore: the user could list the items which should be ignored, represented by XPath statements. Also there would be an opposite option: a list of XPath statements to check and to ignore the rest of the documents. Suggestions The Compare test step can utilize the XMLUnit library for XML and thus expose its function via SoapUI user interface. The Compare step can be similarly used for JSON documents.
Search and replace
I a really miss a search and replace function. It should replace all test objects like testcases, testsuites, properties, request etc and also in groovy scripts and other test resources like description as well. It would be nice if you could have a replace all and a replace current (where you have to confirm each change). You can search and replace directly in the xml file but it is quite cumbersome.
OAS 3.0 tooling support
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.
Allow uppercase in URL in the HTTP Request test step
In soapUI 5.2.2 I have to use a property or modify the xml file directly to be able to test against a URL with mixed case it should just be allowed. Refer to Question on Howfor the the workaround i want to avoid http://community.smartbear.com/t5/SoapUI-Open-Source/How-do-I-create-a-HTTP-Request-URL-with-uppercase-characters/td-p/105180Configuration to allow loading unsigned plugins
Configurationto allow loading unsigned plugins Description Currently SoapUI-5.3.0 allows to load only the plugins which are signed by Smartbear, for security reasons. Thisprecaution prevents to develop, test and use the plugins which are not signed by Smartbear. Asking Smartbear to sign every JAR we need to test is not feasible. The enforcement of signing the plugins is contrary to open source principles. Proposal Introduce a configuration item in SoapUI properties, which allows loading unsigned plugins. The item can be set to false by default, but the user will be able to allow it at his own risk. There can be a short notice about potential risks. Benefits The implementation would allow more freedom and flexibility to both SoapUI contributors and users and encourage people to develop new/custom plugins.An option to ignore SSL certificate issues
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
Tabbed windows, as in modern browsers or Visual Studio
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.SoapUI - Folders in Projects
Right now the only grouping possible is by project, it would be nice to be able to have folders inside this projects. This way the "workbench" can be a little cleaner. Anyway, thanks in advance and thanks for such a helping tool. Best regards and keep up the wood work! Federico.Displaying Groovy script test step result
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. KarelWorkspace support for scripting
Support fordevelopment and execution of generic scripts I would appreciate additional support for scripting: - script console to develop and execute generic Groovy/Javascript scripts (similar to Groovy script test step editor) - list of custom scripts (either stored in a folder or in a workspace configuration xml), with the option to create, save and modify scripts The motivation: there are often situations when I need to execute a script which does not belong to any test, e.g.: - bulk change of a property within a project (or multiple projects) - launch several selected test suits - launch all test suits of selected projects - generate a test project from a list of WSDLs etc. Currently: the projects support scripting: setUp scripts, tearDown scripts, Groovy test steps, Groovy assertions etc. When I need to launch a generic script I have to use an existing project, create a Groovy test step, do the scripting, then do the cleanup. Some other users create a new test project just to develop and debug scripts, then delete it.This is ineffective. If I launch the tests from command line, I cannot use the SoapUI user environment to analyze the test results. The scripting support would provide both -- the efficiency of scripting and the comfort of the user environment.
In Soap UI it would be better if we have Pause and resume options while executing the Test Suite
In Soap UI it would be better if we have Pause and resume options while executing the Test Suite during the run time, so that it would better for debugging purposes. Currenlty we have to cancel the test execute and do the necessary debugging if some thing fails and again we need to execute the test suite from the beginning.SOAP UI Response Window for JSON no support for edit and find words
I worked many years with SOAP UI for SOAP/XML . Useful was the feature that the REsponse windows is actually an editor window where I could directly modify the response text (insert new lines, ) search for keywords,..etc... Now we are moving to JSON and the Reponse window for JSON doesn't allow editing, neither CTRL+F (Find) The only operation that seem work ist CTRL+A and then CTRL+C for copy. Hence a separate editor is needed... I am using SOAPUI 5.2.1 It shouldn't be a big change to allow editing in that windows as well, since you already allow editin in the SOAP response window. Most probably some detail in the configuration of the windows object for editor window called. OR the problem is that that window doesn't get the focus when pointed & click by the mouse. Hence the CTRL etc are sent to the neavigation pane. It would be good to have this fixed in a next release. Thank you! Adrian
Make Soap UI compatible with Selenium 3.X
Soap UI 5.x versions are currently unusable from the last 2.x versions of selenium up to version 3.X. This is due to dependency mismatches in the http client which prevent inter-operability in the same JVM. Soap UI is a viable solutions for web testing with Selenium, we used it for many years in the past. Currently it is unusable. This is a very nice way to do web testing when it works, and many folks have asked about this.
AUTO RESOLVE SCHEMA CHANGES AT PROJECT LEVEL
Schema inference is definitely a good way to auto resolve schema conflicts if there are one or two test cases for which a schema change will affect. But if there are say some 600 test cases on a single Rest URI then it's pretty hard to go to each test case and then click on "Resolve all conflict". So if we have this option at the menu/context menu level we can achieve auto schema resolve at all points(like Project level, Test Suite level, Test case level or Test Step level). Also a reverting option of what has been done would also be a great value add.
Provide a better hint re. the necessary input for "Contains Assertions" with reg-exp. enabled.
You may want to provide a corresponding hint in the check-box's text (or at least its hover-text), because that's not exactly intuitive. Without the reg-exp checkbox being ticket one needs to provide a substring only that has to be contained somewhere in the response. With the check box ticked, it needs to match the entire response. Please make that difference more explicit! Background here: Re: Contains assertion with option "Use Token as regular expression" not workingAssertion cloning
It would be great to have facility to clone assertions to multiple TestCases in one go. Current support is to target only one test case in a test suite. The same idea can be extended to choose multiple target TestSuites and in each Suite select all/specific TestCases to copy assertions to. Thanks for considering.restrequest with retries
The responsiveness of a system under test may vary widely depending on the environment. Tests that worked in one run may fail in the next run if the system took longer than expected to respond, then pass again in another run. Such variable responsiveness may be acceptable, depending on product requirements. Idea: Enhance restrequest steps to support retries. Let the test developer specify the max # attempts as well as the delay between attempts (e.g. millisecond). Enhance logging to record the #attempts required until test completion (e.g. test step completed after 3 attempts and 3984 milliseconds delay) or similar. Set default max #attempts=1, with default delay blank or some value that is grayed out when max #attempts=1. Enable setting of the delay when the user sets max #attempts > 1. Benefits: provide some resilience to functional tests so they continue to succed (from a functional perspective) even when system responsiveness varies provide logging information that lets other tools track the evolution of system responsiveness allows tests to simulate how real components in a loosely-coupled system would interact with each other (i.e. with retries) Other thoughts The "number of retries" can be confused with the "number of attempts", the latter being one more than the former. So the name for such a capability would have to be chosen and documented carefully. Creating a separate step type would avoid modifying the existing restrequest type (less change to existing step). However the existing restrequest type could be enhanced in a backwards compatible way and avoids having to explain when to use the old restrequest step and when to use the new one (more transparent).Rest call - if "The content can not be viewed as XML" - display other format
Let's say I make a call to a rest api and the response is json. When the SOAPUI REST call has completed, it will still default to XML as the default response type (assumedly because SoapUI is very XML centric due to it's Soap connection). You should spy the resulting content using response header or content. Or maybe it is not working because my particular content-type is using charset=UTF-8. Content-Type application/json;charset=UTF-8SoapUI - Remember path of last added wsdl
If you need to add two or more WSDLs from your file system, every fileyou add starts the "browse" dialog from SoapUI's instalation folder. It would help a lot if the last path is remebered, so no need to navigate to the directory every time. Thanks again. Best regards, Federico.Tutorial SOAP Security Header with C#
Hi Community, I'm trying to add a security header to a soap-message via C# like SOAPUI it does. Is there a tutorial describing this? Her is the setup I'm using for request by soapui. I've found a topic https://community.smartbear.com/t5/SoapUI-Open-Source-Questions/How-does-SOAPUI-calculate-the-SignatureValue-for-a-SignedInfo/td-p/174176 where a similar problem is mentioned. I've copied code from this thread. I also have different hash values for BinarySecurityToken generated once by soapui and another generated by C#. BinarySecurityToken is a constant value that I could insert hard coded. But the signature value depends on the definition of the body and will change every request. Many thanks for your help. Kind regard, navguruRequest to restore the feature of importing ReadyAPI project to SoapUI (free versin)
Hello: I have been using SoapUI long since Eviware era (2008). In the past, I never had any issue to import projects from SoapUI Pro. I used to use a licensed version of SoapUI Pro for my development and then deploy those developed projects in different machines where the free version SoapUI used to run. As a test developer, I would like to see that feature of importing projects from Pro (ReadyAPI) to Free (SoapUI). But alas! recently that feature was taken away and just today I discovered that I am no more able to import projects in SoapUI which was developed on ReadyAPI. As a long time patron of SoapUI and ReadyAPI, I would request to restore back that convenience. /jamil.
Test different resource values in SOAP UI
Hi, I am trying to create tests for the endpoint which ends like this: /account/id where id can have different values. In SOAP UI I want to test whether the correct value return 200, and other incorrect values return 400, so I would like to have tests: 1. /account/1234 - correct 2. /account/abc - incorrect However I am unable to change the values of the resource in Test Cases in SOAP UI as it is hardcoded: Is there any way I can change resource depending on the test?SOAPUI is sending duplicate header parameters
Hi, I'm sending a POST request using SOAPUI free version and, I don't know why, in the request I see header's parameters duplicate. This cause of course a bad request response. I tried to close the application and I reboot my pc but It didn't work. Anybody has some suggestion? ThanksUnable to use the test runner in ReadyAPI 3.10.2
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)OAuth2
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? 'Make SOAPUI work with Hermes JMS again
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.0export json swagger with response member details
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":{}}}}}Option to switch logging tabs from bottom to the right
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.Endpoint / Resource / Parameters appearance and UI
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.Allow longer resource to be used.
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.New test 'collection'
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 theready-api-maven-plugin and execute them in the order they are specified -- obviously for this to work, you would have to leave <testCase> empty.Update JsonPath library version
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.
SoapUI Feature Requests
69 Posts
