Contributions
Re: Soap UI Pro sends a URL with Junk values
richie: No I havent parameterised the action tag also content of the tag are not dynamic as its just a URL. Posting the content would be difficult as it contains sensitive data. I even tried to delete the action url but then too it was sent as part of request.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.7KViews0likes0CommentsRe: Soap UI Pro sends a URL with Junk values
Radfordwrote: The following documentation: https://support.smartbear.com/readyapi/docs/projects/ui/request-properties/soap.html with regard to the "Skip SOAP Action" propertystates "If true, excludes the action value from the request header". From your screenshot it looks like it's available in you rather old version of SOAP UI Pro, have you tried setting this property? Radford:Yes I just tried that but no luck. Although the action was also sent as part of header earlier which now isnt, but Action URL is still part of request body. I even tried to delete the action url but then too it was sent as part of request.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.7KViews0likes0CommentsRe: Soap UI Pro sends a URL with Junk values
Radford:Yes I just tried that but no luck. Although the action was also sent as part of header earlier which now isnt, but Action URL is still part of request body. I even tried to delete the action url but then too it was sent as part of request.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.7KViews0likes0CommentsSoap UI Pro sends a URL with Junk values
Hi All, I have a request XML defined but when I try to execute it, the tool adds "{}" and "/" to url in action tag (highlighted in bold below). Due to this I am getting error in response. I have also attached the settings of the project. Version: 5.1.2, cant update it due to restrictions org wise. Req XML: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:vh="http://XXXX/soap/header/v-header-v1-8.xsd" xmlns:evt="http://XXXX/soap/header/ev-test-header-v1-1.xsd"> <soapenv:Header> <wsse:Security> <wsse:UsernameToken> <wsse:Username>ABC</wsse:Username> <wsse:Password>XYZ</wsse:Password> </wsse:UsernameToken> </wsse:Security> <wsa:To>URL</wsa:To> <wsa:MessageID>urn:123456</wsa:MessageID> <vh:MemberCode>ABCD</vh:MemberCode> <vh:BranchCode>1234</vh:BranchCode> <wsa:Action>http://HOST/Verify</wsa:Action></soapenv:Header> On execution the request changes to: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:vh="http://XXXX/soap/header/v-header-v1-8.xsd" xmlns:evt="http://XXXX/soap/header/ev-test-header-v1-1.xsd"> <soapenv:Header> <wsse:Security> <wsse:UsernameToken> <wsse:Username>ABC</wsse:Username> <wsse:Password>XYZ</wsse:Password> </wsse:UsernameToken> </wsse:Security> <wsa:To>URL</wsa:To> <wsa:MessageID>urn:123456</wsa:MessageID> <vh:MemberCode>ABCD</vh:MemberCode> <vh:BranchCode>1234</vh:BranchCode> <wsa:Action>{http://schemas.xmlsoap.org/wsdl/http/}//HOST/VerifySolved6 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.7KViews0likes7CommentsRe: Soap UI report in Jenkins
Radford: I tried the steps you mentioned and it worked fine, but the HTML report contains very less detail like test case pass/fail, and time taken. is this expected? or I can get more details into it. I understand there is nothing much which comes out of a soap ui Test but just for information wanted to know. As of now I am using workspace to store my project and run my test cases, hence i havent used -f option. Any idea -f option needs a linux machine path or workpace path?7 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.2KViews0likes2Comments- 7 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.3KViews0likes0Comments