Contributions
SoapUITestCaseRunner SchemaCompliance Assertions
Hi, While running SoapUITestCaseRunner with out tests we notice that the "Schema Compliance" assertion isn't regarding the -h flag. Is this the correct behaviour? Since we're developing tests on our localhosts and running the tests on different hosts we use the -h flag to set which host to make the calls on. The schema compliance assertion points to a WSDL definition and it would be preferable if the URL was substituted just as the request endpoints. http:// : /services/PortType?wsdl2.1KViews0likes4Comments- 874Views0likes0Comments
Re: Nullpointer when running testrunner on solaris console
Great. I'm guessing that the error originates from here: protected AbstractHttpRequest( T config, AbstractHttpOperation parent, String icon, boolean forLoadTest ) { super( config, parent, icon ); if( !forLoadTest && !UISupport.isHeadless() ) { -->probably not run at all? iconAnimator = initIconAnimator(); --> addSubmitListener( iconAnimator ); } initAttachments(); dumpFile = new SettingPathPropertySupport( this, DUMP_FILE ); }874Views0likes0CommentsNullpointer when running testrunner on solaris console
I'm trying to run the testrunner.sh script from a solaris console. I pass in a test.xml file containing my testcases. I can see that the tests are run, the server is responding correctly, but when the response comes back I get a NullPointerException(Stacktrace below). Running the same test on my Windows machine (in cygwin/bash so I run the .sh script there as well, unmodified) is working just fine. So I'm guessing that it has something to do with running java in headless mode on a remote console without a display. I tried to set the headless mode using: -Djava.awt.headless=true But I get the same error. Stacktrace: 10:47:31,069 ERROR [WsdlTestCaseRunner] Exception during TestCase Execution java.lang.NullPointerException at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequest.getIcon(WsdlTestRequest.java:283) at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequest$PropertyChangeNotifier. (WsdlTestRequest.java:179) at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequest.assertResponse(WsdlTestRequest.java:158) at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequest.setResponse(WsdlTestRequest.java:152) at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequestStep.run(WsdlTestRequestStep.java:322) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runTestStep(WsdlTestCaseRunner.java:256) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.run(WsdlTestCaseRunner.java:175) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.start(WsdlTestCaseRunner.java:79) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCase.run(WsdlTestCase.java:535) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCase.run(WsdlTestCase.java:49) at com.eviware.soapui.tools.SoapUITestCaseRunner.runTestCase(SoapUITestCaseRunner.java:496) at com.eviware.soapui.tools.SoapUITestCaseRunner.runSuite(SoapUITestCaseRunner.java:454) at com.eviware.soapui.tools.SoapUITestCaseRunner.runRunner(SoapUITestCaseRunner.java:331) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:122) at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:74) at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:95)2.6KViews0likes5CommentsNullpointer with Maven plugin when running tools
I've created a test project just to try out the maven plugin (I want to run WS-I compliance test and automated WS tests during builds). Testing the Webservices using the SOAPui project file and the maven plugin works just fine, but when I try to use the tool target for the maven plugin I get a NullPointerException. mvn eviware:maven-soapui-plugin:tool java.lang.NullPointerException at com.eviware.soapui.impl.wsdl.actions.iface.tools.wsi.WSIAnalyzeAction.generate(WSIAnalyzeAction.java:101) at com.eviware.soapui.impl.wsdl.actions.iface.tools.wsi.WSIAnalyzeAction.generate(WSIAnalyzeAction.java:58) at com.eviware.soapui.impl.wsdl.actions.iface.tools.support.AbstractToolsAction.perform(AbstractToolsAction.java:116) at com.eviware.soapui.tools.SoapUIToolRunner.runTool(SoapUIToolRunner.java:203) at com.eviware.soapui.tools.SoapUIToolRunner.runRunner(SoapUIToolRunner.java:115) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:114) at com.eviware.soapui.maven2.ToolMojo.execute(ToolMojo.java:59) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Opening up the code shows us that: AbstractToolsAction line116: generate(initValues( ( T ) target, param ), UISupport.getToolHost(), ( T ) target ); UISupport.getToolHost() does return a NULL object. No ToolHost is set anywhere in the call chain, setting it with: com.eviware.soapui.support.UISupport.setToolHost(new com.eviware.soapui.tools.SoapUIToolRunner()); makes the maven plugin work just fine. Is this a bug or am I doing something wrong?2.1KViews0likes3Comments