gordillo_ramon
Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Can i automate regression testing using soapui?
Sure. We built a framework for regression testing including mock launching for endpoints, and this can be run from command line and integrated on a CI platform (for example, we used jenkins). The only limitation is if all your tests can be done using SoapUI (SOAP/REST services 99% sure).6.5KViews0likes0CommentsWS-I Support
Hi. I have seen that last version (5.0.0) supports WS-I (BP 1.1) in WSDL checks and messages. We have a request to test a WebService product against WS-I BP 1.2 (for SOAP 1.1 compliance) and BP 2.0 (for SOAP 1.2 compliance). Is there any experience with these requirements? Any community project that supports BP 1.2 and BP 2.0 testsuites/mockservices? Thanks in advance. Ramon624Views0likes0CommentsREST Property Expansion
Hi all. I have tried to use the property expansion in a POST REST request, in the body part, but every time I get the property unexpanded, just the literal "${..." I get the same property expanded in the headers. Is it possible to use it in the body? TIA. RamonSolved2.7KViews0likes5CommentsRe: SoapUI + hermes on linux - configuration issue
Only if it could help other people... I faced the same issue with 4.0.1. After looking at this thread, I did not see any cglib in soapui/lib. When I was about to give up, I checked the size of hermes-1.14.jar and the hermes 1.14 distribution jar file (hermes.jar) and found it was different. So I removed hermes-1.14.jar and link this file to the original distribution and voila! Now it works perfectly. Any SmartBear guy can confirm if the hermes-1.14.jar in the soapui distribution is the final release, or any RC? Regards.1KViews0likes0CommentsUTF-8 double encoding in URL for REST resources
Hi. I set up a REST project with a test case for calling the server. The resource URL has a parameter that needs to be encoded (te:+44...), but I get a surprise when I saw the url like "tel%253A%252B447309700001" instead of the expected "tel%3A%2B447309700001". Attached the screenshot where you see that the url over the request is correctly encoded, but the url in the post is "double" encoded (the "%" has been encoded again). Can you confirm if there is a bug related with double encoding in REST urls? Many thanks. Ramon2.1KViews0likes1Comment