SoapUI Groovy API documentation [closed]

Closed. This question is seeking recommendations for books, tools, software libraries, and more. It does not meet Stack Overflow guidelines guidelines. It is开发者_Python百科 not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 5 years ago.

Improve this question

I'm using Groovy scripts as part of our SoapUI automation efforts.

I tried looking in SoapUI's website for documentation on their object model and how Groovy can be used properly within the testRunner context, but I was unable to find anything helpful yet. Since the Groovy editor SoapUI supplies does not have auto-completion, it is hard to guess which properties each object has.

Is there any good documentation about the APIs and how to use them?

---

Please note there are TWO sets of APIs:

1. Pro Version: http://www.soapui.org/apidocs/pro/index.html

2. Free Version: http://www.soapui.org/apidocs/index.html

And the groovy docs: http://groovy.codehaus.org/groovy-jdk/

---

Found it eventually - I was too set on finding groovy documentation instead of looking at the Java API documentation.

The entry point to the model is a testRunner which is actually a WsdlTestCaseRunner object.
Its documentation can be found here: http://www.soapui.org/apidocs/com/eviware/soapui/impl/wsdl/testcase/WsdlTestCaseRunner.html

From that page I can navigate to the rest of the model if I want.

---

SmartBear released Ready API which is further enhancement to SoapUI Pro (both are paid tools) which has context sense help while doing groovy scripting.

And the following link might be helpful to scripting.

Also would like to add a point that in groovy script test step, the following instance variables are available as you would see the same on the groovy script panel, top of the editor.

1. context
2. log
3. testRunner

And the small tip is that if you type log.info in the script, you can see some interesting stuff in the log.

For example you can try

log.info testRunner