TooDizzyOccasional ContributorJoined 9 years ago9 Posts1 LikeLikes received2 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsRe: Loop over an XML database i.e. a SOAP response and if you have a nested element use similar approach: "*:product/*:id/text()". Anonymous: Not very elegant! Re: Loop over an XML database i.e. a SOAP response The answer was found here: https://community.smartbear.com/t5/SoapUI-NG/Better-Support-of-XML-Data-Sources/td-p/41235/page/2 Very important to prefix your column XPath with "*:". Who knew? Anyway it working now. Loop over an XML database i.e. a SOAP response Hi Guys, I can't seem to get around how to loop over the values inside a SOAP request. I figure that I need an XML datasource. That's fine, but I really can't get it to work. I'm using XPath to query the XML, but I'm not even able to get a single value out of the SOAP response. I'm most likely just using the too incorrectly. Anyone that got this working? Re: Composite build will not execute on build server, but runs locally found the problem. I had a . in the build name. On the jenkins server this results on a folder structure with the build name as the checkout path. Here we then have "." in the path. Perfectly normal and legit on linux, but it was too much for the Ready API plugin. Sounds like a path related in the plugin. /Tue Composite build will not execute on build server, but runs locally Hi Guys, I'm having a serious problem executing my SOAP UI Pro build. I'm running Ready API 1.8.5 and my project is a composite project. When I run it locally (the maven build) everything runs fine and the test starts as expected. Running the same build on our build server results in the below error. It can't, for some weird reason, suddenly not find the project.xml. It's a composite project so I have only specified the folder of the project - and it runs locally. The build server has a valid license installed. For the maven build I use the latest available plug-in: <groupId>com.smartbear</groupId> <artifactId>ready-api-maven-plugin</artifactId> <version>1.8.1</version> Here the exception: t com.eviware.soapui.impl.wsdl.WsdlProjectPro.<init>(WsdlProjectPro.java:180) at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(WsdlProjectProFactory.java:92) at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(WsdlProjectProFactory.java:1) at com.smartbear.ready.cmd.runner.AbstractSoapUIRunner.getWsdlProject(AbstractSoapUIRunner.java:378) at com.smartbear.ready.cmd.runner.SoapUITestCaseRunner.runRunner(SoapUITestCaseRunner.java:356) at com.smartbear.ready.cmd.runner.pro.SoapUIProTestCaseRunner.runRunner(SoapUIProTestCaseRunner.java:98) at com.smartbear.ready.cmd.runner.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:257) at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:152) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.jvnet.hudson.maven3.launcher.Maven32Launcher.main(Maven32Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven32Main.launch(Maven32Main.java:186) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.maven.Maven3Builder.call(Maven3Builder.java:136) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1276) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1263) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345) at com.eviware.soapui.config.SoapuiProjectDocumentConfig$Factory.parse(Unknown Source) at com.eviware.soapui.impl.wsdl.WsdlProjectPro.b(WsdlProjectPro.java:541) at com.eviware.soapui.impl.wsdl.WsdlProjectPro.loadProject(WsdlProjectPro.java:354) ... 42 more Caused by: org.xml.sax.SAXParseException; systemId: file:; lineNumber: 1; columnNumber: 1; Unexpected element: CDATA at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038) at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723) at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454) ... 48 more Any ideas to resolve this are most welcome. Thanks! /Tue SolvedRe: Can't generate PDF report with the maven plugin Finally got it working. It seems that the <reportName> tag is not the filename of the report, but the name of the report template/type. Not that clear from the docs. <reportName>TestSuite Report</reportName> Can't generate PDF report with the maven plugin Hi Guys, Running Ready API 1.8 with a pro license for SOAP UI. I've created the nice looking PDF report for a test suite with the application and now I also want to do this using the maven plugni. This I cannot do for some reason. I set all these flags in the configuration section, but no report are being generated. If you have a good example POM I can use - where you generate a PDF report - I would be very happy. <printReport>true</printReport> <coverage>true</coverage> <exportAll>true</exportAll> <reportFormat>"PDF"</reportFormat> <reportType>TestSuite Report</reportType> <reportName>PDF Report</reportName SolvedRe: Can't build composite SOAP UI PRO project with the maven plugin Perfect it works now! I thought I tried that a million times. I guess it took a million and 1 attempts. Thanks! Can't build composite SOAP UI PRO project with the maven plugin Hi Guys, We are running the bleeding edge of ReadyAPI (version 1.8.0) and have the pro license for the SOAP UI NG PRO product. This is all fine and working. I am for some reason not able to execute my tests with the provided 1.8.0 version of the maven plugin. Our project is a composite project and therefore does not have a project file; there's only a settings.xml file. When running my test it complains about not being able to find the project file. There's none, so it makes sense. How do I configure the maven plugin to execute my SOAP UI test cases when the project is a composite project? /Tue