Contributions
SOAP Mock Response Start Step still disappearing (SoapUI 5.6)
Hi, See https://community.smartbear.com/t5/SoapUI-Open-Source/SOAP-Mock-Response-Start-Step-disappearing/m-p/186656 This is still broken in SoapUI 5.6. Whenever you rename an assertion in a step that is referenced as a Start Step for a SOAP Mock Response, that reference also gets renamed to the new assertion name. Kind regards744Views0likes1CommentRe: SoapUI on JDK11
Hi. For my specific use case, where I am using the soapui library from within a unit test, the following two-part workaround solves it for me: 1. Add this dependency exclusion to the pom.xml: <exclusion> <groupId>com.smartbear.utils.analytics</groupId> <artifactId>out-app-analytics-provider</artifactId> </exclusion> 2. Disable analytics: com.eviware.soapui.SoapUI.getSettings().setBoolean(UISettings.DISABLE_ANALYTICS, true); Kind regards, Jimmy1.8KViews1like1CommentRe: SOAP Mock Response Start Step disappearing
It looks like, when changing the NAME of an assertion in the start step, it also incorrectly changes the startStep name of the SOAP Mock Response to the name of the assertion. I suspect the problem is here somewhere? https://github.com/SmartBear/soapui/blob/fe41852da853365c8be1ab331f713462695fd519/soapui/src/main/java/com/eviware/soapui/impl/wsdl/teststeps/WsdlMockResponseTestStep.java#L767935Views0likes0CommentsRe: SOAP Mock Response Start Step disappearing
When I look at the XML source of the SoapUI project, it looks like the startStep is not actually disappearing, but rather replaced by the name of an assertion in that test case? Strange.. and still haven't figured out what actually triggers this.946Views0likes1CommentSOAP Mock Response Start Step disappearing
Hi, I regularly have a problem where the "Start Step" configuration of some "SOAP Mock Response" test steps in my project are disappearing. I haven't figured out what exactly is triggering this, but it is very annoying. Has anyone else ran into this problem? I'm on SoapUI 5.5.0. Kind regards, Jimmy984Views0likes2CommentsRe: SoapUI 5.5.0 will not run project or suites - Toolkit not initialized error
It fails for me if I disable showing the Endpoint explorer and the startup page. It fails both on Windows 7 and Windows 10. Tue Mar 05 19:36:57 CET 2019:ERROR:Exception during Test Execution java.lang.IllegalStateException: Toolkit not initialized at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:273) at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:268) at javafx.application.Platform.runLater(Platform.java:83) at com.eviware.soapui.impl.wsdl.panels.testsuite.WsdlTestSuiteDesktopPanel$InternalTestSuiteRunListener.afterTestCase(WsdlTestSuiteDesktopPanel.java:430) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestSuiteRunner.notifyAfterRunTestCase(WsdlTestSuiteRunner.java:200) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestSuiteRunner.runSequential(WsdlTestSuiteRunner.java:130) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestSuiteRunner.internalRun(WsdlTestSuiteRunner.java:94) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestSuiteRunner.internalRun(WsdlTestSuiteRunner.java:46) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:128) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)5.2KViews1like1CommentMockResponse step invoke multiple times
Hi, I have a soapUI test case where a MockResponse teststep should be invoked multiple times (5x). I want to assert that a certain field in the received mock requests is 'X' for the first 4 invocations, and 'Y' for the 5th invocation. But I can't seem to figure out how to do this. If I add a groovy script assertion it is apparently only invoked for the first mock request?15 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes1Comment