oh, sorry, my fault; try changing the method declarations in the code to use WsdlRequest instead of Request as the request argument type (in the com.eviware.soapui.impl.wsdl.submit package)..
use the XmlUtils.declareXPathNamespaces( String xmlString ) method, which will return the namespace declarations for all namespaces used in the specified xml string.
this is unfortunately a known issue with the WSDL validation; it doesn't expand inline attachments before validating.. it's on our list for fixes though.. sorry for the inconvenience..
hm, are you running from SVN or the latest build? This is nothing to worry about, it just says that the demo-listeners.xml file specified a listener that isn't available..
just to make sure; are you actually transferring the username/password TestCase properties in the authenticate TestCase to the corresponding username/password in the requests where you want to use them (using a Poperty-transfer)? (Just because they are named the same doesn't mean they will automatically get each others values..)
I've create a blog-entry that tries to explain this in little more detail when used with LoadTests, have a look at http://www.eviware.com/blogs/oleblog/?p=194 and please feel free to comment, question, etc..
you can always navigate back "down" the tree with either xXCount/getXXAt/getXXByName methods, for example testSuite.testCaseCount / testSuite.getTestCaseAt( ix ), or XXs[name], for example project.testSuites["TestSuite 1"]
You can get the workspace with project.workspace and then another project with getProjectByName.. A complete example:
sure, to set a property all you need to do is call the corresponding setPropertyValue, ie
testCase.setPropertyValue( name, value )
or
project.setPropertyValue( name, value )
if the property doesn't exist, it will be created first. Depending on from where you are doing this, access to the object model differs. For example from inside Groovy Script TestStep, you would do
testRunner.testCase.testSuite.project
to get the project. Let me know your specific context and I'll help you forward!
Also, you can set global properties with
com.eviware.soapui.SoapUI.globalProperties.setPropertyValue( name, value )
If you are willing to use the 2.5 beta version, you can use the new inline-scripting possibility as described at http://www.eviware.com/blogs/oleblog/?p=6, otherwise your property-transfer should work providing that the property it transfers has a unique value. How are you generating it now?
to "celebrate" the 2.5 beta release (http://www.eviware.com/content/view/128/1/), I've finally started a blog which will be mainly focused on soapUI related subjects (announcements, tips&tricks, tutorials) and industry news/discussions. Have a look at http://www.eviware.com/blogs/oleblog/ and please feel free to comment, suggest and complain!
Show Posts
