Contributions
Re: Using global property transfert with command line
No problem. For your null object question... Open a new topic in the forum for this question. In the new topic, please post a snippet or attach the entire log so we can see more clearly what the error is, and where it is coming from.1.5KViews0likes0CommentsRe: Using global property transfert with command line
Instead of a "TestCase"-level property, use a Project level: <barcode>${#Project#barcode}</barcode> Then when you call testrunner, add the -P argument: ./testrunner.sh -Pbarcode=500 myProject.xml The -P option will set a Project level property after the project loads. The -P option will override an existing value that is saved in the soapui project.1.5KViews0likes0CommentsRe: Using entire SOAP response directly into a new SOAP request
Also, just an FYI... Are you aware that the Property Transfer step is able to do what you want? It can transfer all the child nodes of one parent node in a Response inside a node of a Request. But this is just a one time thing. I understand you want to store the XML and use it many times from any test case. See this post for details http://www.soapui.org/forum/viewtopic.php?t=63711.3KViews0likes0CommentsRe: Using entire SOAP response directly into a new SOAP request
Thanks for the details. I think I understand now. I am unable to reproduce this issue where data transferred from Response to Project property is enclosed with CDATA tags. Unfortunately, I don't have much experience with transferring XML nodes with child nodes in and out of properties. What version of soapUI are you using? Is is Pro or Free version? Have a look at this page to see if anything here is helpful for your scenario: http://www.soapui.org/Functional-Testin ... cdata.html - especially the section titled "Property Transfers and CDATA"1.3KViews0likes0CommentsRe: Disable/Enable Assertion Based on DataSource Property
Ok, briefly tried to figure this one out on my own, but then decided to just search. https://www.eviware.com/forum/viewtopic.php?t=859 Using info from above post...change your script to something like: step = testRunner.testCase.testSteps["submitCheck-Base"] noFault = step.assertions["NoFaultAssertion"] fault = step.assertions["FaultAssertion"] if (${DataSource#Assertion} == "accept") { noFault.disabled = true fault.disabled = false } else if (${DataSource#Assertion} == "error") { noFault.disabled = false fault.disabled = true } else { noFault.disabled = false fault.disabled = false } Or, more concise (perhaps not as efficient): step = testRunner.testCase.testSteps["submitCheck-Base"] noFault = step.assertions["NoFaultAssertion"] fault = step.assertions["FaultAssertion"] noFault.disabled = false fault.disabled = false if (${DataSource#Assertion} == "accept") noFault.disabled = true if (${DataSource#Assertion} == "error") fault.disabled = true1.5KViews0likes0CommentsRe: When Test Request is cloned endpoints are not cloned
I manage my endpoints (add all possible endpoints I might want) at the WSDL level. Then they are all displayed as choices in any TestRequest for a operation defined by that WSDL. Even better, use only one endpoint with IP and Port defined using properties. Then modify the property value when you want to change endpoints.14 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsRe: Feature Request - Commenting
There is a "Description" element for each Test Case. This is where I put any kind of summary, pre-conditions, expected results, requirements, etc. Double-click a test case. Click the 'Description' tab. One neat feature is that if this Description field contains any text, then mousing over the test case in the navigation tree will display a popup 'tool tip' style window that displays contents of the Description field. Same concept exists for TestSuites and Project. I know of no such feature for individual test steps. Not sure I would want to have that level of detail cluttering my view.14 years agoPlace ReadyAPI QuestionsReadyAPI Questions705Views0likes0CommentsRe: Call Compiled Java Class for WMQ Request
Hi fstach, welcome! Put your compiled JAR file (any any additional supporting libs) into <soapui_program_dir>/bin/ext Then in a Groovy Test Step withing soapUI, import your java package e.g.: import name.of.package.*; Create an object of your class and call methods on it. As for reading your 'request_message.xml' I'm not sure at the moment. Maybe either store it as a property in soapUI, or use groovy/java IO methods to read from the filesystem. Have a look at these posts for maybe some more clear explantion: viewtopic.php?f=5&t=7093 viewtopic.php?f=2&t=7052 Any of this make sense?819Views0likes0Comments