Hi Markusreiser,
Our R&D team are fixing this issue right now. Could you please install the latest nightly build in several hours?
I use the snapshop from the 18.09.2015.
The error isn't fixed. It is a little bit better. If I run the Testcase the first time all is ok. If I run the Testcase a second time I got another NullPointerException Exception.
java.lang.NullPointerException
at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.setVariable(SoapUIGroovyScriptEngine.java:147)
Also other things don't work in this version. I have no time to write this down here.
I now have no more time be a tester for you and I hope that you can fix the main bugs in this version.
Until now I can't use the new version for Ready! API for my projects and i will still use version 1.3.1
Sorry :-(
I have a similar problem. I've raised a ticket on it case number: 00134582
But if we can solve it here - I'll appriciate it.
I'm using Ready API 1.4.1 (and SoapUI NG Pro 1.4.1)
My problem is when I run my test suite with Jenkins using Maven my first test case executes with success but the second test case can't build and fails with the error message seen below:
----------------------------------------
07:16:04,745 INFO [SoapUITestCaseRunner] Running SoapUI testcase [Popular Channels]
07:16:04,747 ERROR [SoapUITestCaseRunner] Failed to set host on endpoint
java.lang.NullPointerException
at com.eviware.soapui.support.Tools.replaceHost(Tools.java:502)
at com.eviware.soapui.tools.AbstractSoapUITestRunner.prepareRequestStep(AbstractSoapUITestRunner.java:146)
at com.eviware.soapui.tools.AbstractSoapUITestRunner.beforeStep(AbstractSoapUITestRunner.java:183)
at com.eviware.soapui.tools.SoapUITestCaseRunner.beforeStep(SoapUITestCaseRunner.java:591)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runBeforeSteps(AbstractTestCaseRunner.java:251)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:208)
at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:138)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:46)
at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:129)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
07:16:04,748 INFO [SoapUITestCaseRunner] running step [PopularChannels]
Missing endpoint for request [PopularChannels]
07:16:05,161 ERROR [AbstractTestRunner] Exception during Test Execution
java.lang.NullPointerException
at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep.run(RestTestRequestStep.java:795)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:212)
at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:138)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:46)
at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:129)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
07:16:05,162 INFO [SoapUITestCaseRunner] Finished running SoapUI testcase [Popular Channels], time taken: 0ms, status: FAILED
--------------------------------------------------
However it works perfectly when I execute it directly from SoapUI NG Pro / Ready API Pro
Hi Aqlive,
Have you got the news from the Ready! API Support Team? If the issue was resolved, please share the solution with us.
