Property transfer version 5.7.2 not removing double quotes.
I am doing property transfer by using the setup script through sql. My request has something which should be in []. I have created the propert transfer like below For the Target i have given like below. $.dispositionIds In the setup script I am giving like below. String dispositionIds = rows.DISPOSTN_ID //Set Property value testRunner.testCase.setPropertyValue( "DISPOSTN_ID", dispositionIds ) After runng the script I am getting the value in double quotes "" like shown below. "dispositionIds":"[1282678]" ---But becasue of the double quotes, My request is thrownig an error saying invalid json. My Colleagesue have a differnt verison soap 5.6.0 and it is working fine for them.19Views1like1CommentREST request with parameters - how to avoid default Content-Transfert-Encoding:quoted-printable ?
Hi, I am facing to an issue (with soapUI version 5.6.0). My POST REST request have two parameters. One of them is a zip file converted in Base64. In Request Raw tab You can see a parameter "Content-Transfert-Encoding" with "quoted-printable". The parameter content contains multiple lines may be due to the Content-Transfert-Encoding parameter value. Expected one line with all the parameter content How to avoid this default value ? In a previous topics one member says that soapUI uses the mail api. And explains that if the primary type of this datasource is "text", and : - If all the bytes in its input stream are US-ASCII, then the encoding is "7bit". - If more than half of the bytes are non-US-ASCII, then the encoding is "base64". - If less than half of the bytes are non-US-ASCII, then the encoding is "quoted-printable". But how to make sure that more than half of the bytes are non-US-ASCII ?553Views0likes5CommentsURL Encoding Not Working in Open Source version 5.7.2
The default behavior for REST query parameters of URL encoding is not working in version 5.7.2. Template parameters with special characters such as "/" are not being encoded causing the backend system to return an HTTP 404 Not Found error. SmartBear Documentation Our configuration14Views0likes0CommentsValidate Server SSL Certificate Against Soap-UI TrustStore
Dear All, I am trying to create a Soap-UI test which does a call against a server with a verified certificate by the CA (Certificate Authority) of my client. We want to validate this against a truststore in soap-ui to validate if the server certificate is indeed the correct, signed certificate we expect. My problem is that my test always succeeds, I actually want my test to succeed when the server presents a signed certificate, but I want the test to fail if the server presents a self-signed certificate. I have tried this with both SoapUI-5.5.0 as well as ReadyAPI 2.8. I have tried starting SoapUI withSSLv3 and TLS in the vmoptions configuration file. I have ofcourse imported the truststore in SoapUI in "Show Project View" menu, and I have done step 4. from the documentation on page: https://www.soapui.org/soapui-projects/ws-security.html Which I expect links my truststore to the project. I have not changed anything in SSL in the Preferences. On the latter page we also notice that in step 1.9 in the Authentication menu the "Incoming WSS:" selection box can be found in the documentation, but it is not there in our application (Both the SoapUI and ReadyAPI). This menu is also not present after uploading the truststore and finishing step 4.2.1KViews0likes1CommentOAuth 2.0 Authorization Code Grant problem
Hi there! We use SoapUI 5.7.0 and we have a problem with a code grant authorization flow. Buildin browser shows "The page could not be loaded" everytime when we try to get the app authorization form (using authorization uri parameter). We noticed that soap ui makes three requests at once: first, just GET request from authorization uri without any parameters, and then twice GET with parameters. In our case the app returns aresponce with http code 400 when we ask form without parameters and return 200 when with. Total: pushing GET ACCESS TOKEN call three requests and one of them wrong. Buildin browser show "The page could not be loaded" in this case. Is there anything we can do to fix this problem? Thanks a lot.48Views1like1CommentCreate a REST TestServer with, Get, Post, Delete, Push
Getting Started with REST Testing in SoapUI | SoapUI Hello! Do you know a good guide for a test server step by step guide. I need to access a test server from C# Desktop WPF application, query data, store data. Thanks in advance. I have no experience with the tool. There are so many settings. How do I start? Regards RobertSecurity configuration for SOAP project using two way SSL with client certificate for auth
Hello Community, I am struggling with configuration of my SOAP project to use client certificate in two way SSL encryption tunnel. I tryied both these guides: -https://www.soapui.org/docs/soapui-projects/ws-security/ -https://www.soapui.org/docs/security-testing/ws-security-settings/ But unfortunatelly I cannot connect to the server. When I use CURL with cert and key it is working like a charm: curl --request GET --url https://XXXX/service1\?WSDL --cert cert.pem--key key.pem OR curl --request POST --url https://XXXX/service1 --cert cert.pem--key key.pem --header 'Content-Type: text/xml' --verbose -d @request.xml However when I create JKS trustore with both of them and I add it to SoapUI, according those guides, I am getting unauthorized response all the time. I tried it on Windows10 and Ubuntu22.04 with SoapUI 5.7.1 Could you please give me nudge or hint how should I configure the SoapUI project to authenticate using 2 way SSL? Thank you.611Views1like5CommentsHow do I set the status of a Script Assertion?
After looking at this documentation, GroovyScriptAssertion (SoapUI 3.0.0 API) (smartbear.com), I've tried the following def currentStep = context.getCurrentStep(); def assertion = currentStep.getAssertionByName('Script Assertion'); assertion.setStatus(com.eviware.soapui.model.testsuite.Assertable.AssertionStatus.FAILED); but I get the error setStatus() exception: groovy.lang.MissingMethodException: No signature of method: com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.GroovyScriptAssertion.setStatus() is applicable for argument types: (com.eviware.soapui.model.testsuite.Assertable$AssertionStatus) values: [FAILED] If I output assertion.getClass() It tells me that assertion's class is com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.GroovyScriptAssertion@71d72a30 What am I doing wrong? I'm using 5.7.1 Edit: If it's not possible to set the status of a test assertion or test step, is it possible to set the status of a testCase?177Views0likes1Comment