wdowling
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: How to get the parameter names in a REST Request
I think based on the code below targetStep.properties.count() would also work to get the total elements in the properties list. but if u google the list structure in groovy it should tell you. def targetStep = testRunner.testCase.getTestStepByName( "Void request - REST Version 1" ); targetStep.properties.each(){element -> if (element.value.toString() ==~ /.*RestTestStepProperty.*/){ // this is a property ffor the request defined by the WADL log.info(element.key) // the name of the property log.info(element.value.getType()) // get the type assigned to the property by the WADL } }572Views0likes0CommentsRe: export responce (XML, Json) in parts to .txt file
I'd expect that you want a data sink step that is either a groovy script or a file type. It depends on what you want to store, what it is to be used for and how it is to be used after storage. What are you attempting to achieve with the storage of the fragment?491Views0likes0CommentsRe: Re: Maven soapUI plugin example
The Maven plugin doesn't require the license. I'm only using the Junit report options so I don't have any examples however they tend to match the values that you would set in the Client. So if you look on the reporting tab for your project you'll find the options listed. The 'reportName' will determine the name of the file and the 'outputFolder' will set where it's going to end up. Based on digging through some of the Jasper Reports stuff it looks like PDF, HTML, XML, Word, RTF, TEXT and XLS are the format options. Please let us know how it goes575Views0likes0CommentsRe: How to get the test step names in a test case using groovy script
This code works for a script step within a test case and will get the names of all the steps for that test case and output them to the log: testRunner.testCase.getTestStepList().each(){ log.info(it.getName()) }1.5KViews1like0CommentsRe: How to invoke a test step(groovy script) from script assertion
Given the limited context of the assertion I can't think of a direct solution to this. However as it is possible to get the result of a script step which is causing the script to execute I would suggest that a possible workaround would be to write a script step that causes the execution of a test Step and call context.expand on the script step #result.498Views0likes0CommentsRe: How to run soapUI test suites from Hudson continuous integration tool
You need to have the project able to be built under maven. There are basic instructions here http://www.soapui.org/plugin/maven2/index.html We have it set-up so that the SoapUI project is stored under SVN, with all test data located in sub dir's of the checkout and referenced using relative paths. We have a pom.xml at the top level of the repository that defines the target as verify and the upstream job for the successful build and deploy of the system triggers this job741Views0likes0CommentsRe: messageExchange not recognised
I expect that the MessageExchange context is not available to you in the script. You will have to get the response from the request directly. def holder = groovyUtils.getXmlHolder(testRunner.testCase.testSteps["XXXStepName"].testRequest.response.getContentAsXml()); should work.7.5KViews0likes0Comments