Contributions
Second mock in TestCase fails - Open SoapUi 5.5.0
Hi We encountered an issue with soapUI project, which consists of testCases with two mockResponse steps. Mock responses refer to the same service (WSDL) but not necessarily, the same operation (soapAction) within the service. The project is run in batch/non-interactive mode, using soapUI 5.5.0. The poject fails on random testCases. Typical log content looks like this: build 16-Dec-2020 08:25:28 08:25:28,361 INFO[SoapUITestCaseRunner]running step[przetworzWynik] build 16-Dec-2020 08:25:28 08:25:28,405 INFO[WsdlMockDispatcher]Mounted WSDL for interface[someservice.obslugaZlecenPlatniczych]at[/test/obslugaZlecenPlatniczych?WSDL] build 16-Dec-2020 08:25:28 08:25:28,406 INFO[JettyMockEngine]Started mockService[przetworzWynik]on port[8088]at path[/test/obslugaZlecenPlatniczych] build 16-Dec-2020 08:25:52 08:25:52,391 ERROR[SoapUI]An error occurred [Missing operation for soapAction[zlozZlecenie]and body element [ Unknown macro: {http} zlozZlecenieWejscie] with SOAP Version[SOAP 1.1]], see error log for details error 16-Dec-2020 08:25:52 com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction[zlozZlecenie]and body element [ Unknown macro: {http} zlozZlecenieWejscie] with SOAP Version[SOAP 1.1] error 16-Dec-2020 08:25:52 at com.eviware.soapui.impl.wsdl.support.soap.SoapUtils.findOperationForRequest(SoapUtils.java:328) error 16-Dec-2020 08:25:52 at com.eviware.soapui.impl.wsdl.mock.WsdlMockDispatcher.dispatchPostRequest(WsdlMockDispatcher.java:192) error 16-Dec-2020 08:25:52 at com.eviware.soapui.impl.wsdl.mock.WsdlMockDispatcher.dispatchRequest(WsdlMockDispatcher.java:114) error 16-Dec-2020 08:25:52 at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchRequest(WsdlMockRunner.java:144) error 16-Dec-2020 08:25:52 at com.eviware.soapui.monitor.JettyMockEngine$ServerHandler.handle(JettyMockEngine.java:604) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.Server.handle(Server.java:326) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:843) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) error 16-Dec-2020 08:25:52 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) error 16-Dec-2020 08:25:52 at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) error 16-Dec-2020 08:25:52 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) error 16-Dec-2020 08:25:52 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) error 16-Dec-2020 08:25:52 at java.lang.Thread.run(Thread.java:748) build 16-Dec-2020 08:25:57 in onMockResult for[przetworzWynik]for result 1253875385 build 16-Dec-2020 08:25:57 Got mockrequest to[przetworzWynik] If testCases have only one mockResponse there is no problem. I see some posts referring to some old problems with second mock run, but quite old and not exactly like that. Does anybody had similar problem? Regards Jaroslaw453Views0likes0CommentsRe: Schema Compliance Assertion - property expansion
Thanks to SmartBear support I learnt that: a) property expansion in Schema Compliance Assertion works in ReadyAPI b) property expansion in Schema Compliance Assertion is not available / doesn't work in SoapUI Open Source. I was adviced to create a new request: https://github.com/SmartBear/soapui/issues/584 and hope for the best... Happy New Year everyone!458Views0likes0CommentsSchema Compliance Assertion - property expansion
Hi I'm pretty sure that in previous versions of Soap UI (somewhere around ReadyApi 2.4.0) it was possible to define Schema Compliance Assertion dynamically using property expansion, like: ${#Project#service_address}/some.service?wsdl Judging by this I'm not mistaken, it worked in the past: https://community.smartbear.com/t5/API-Functional-Security-Testing/Schema-Compliance/m-p/7315 It looks like with SoapUI 5.6.0 it is not possible anymore or something changed in the way it should be used. So the first question is: is it not possible in that version? I see I'm not the first one stumbling upon it: https://community.smartbear.com/t5/SoapUI-Open-Source/Dynamic-Schema-Compliance-Assertions/m-p/40934 I've tried this solution via groovy: https://community.smartbear.com/t5/SoapUI-Open-Source/Schema-Compliance-Assertion-setting-Definition-URL-with-Groovy/m-p/136565#M23261 Somehow it doesn't work for me as expected. It changes url only after closing and opening project again. Which is contrary to the purpose of it - being dynamically changed during execution. So, to reiterate: 1. is it possible to use property expansion in Schema Compliance Assertion? 2. if not, how to change url in this assertion dynamically during test execution? Regards Jarek551Views0likes1Comment