Forum Discussion

sprice090161's avatar
sprice090161
Contributor
7 years ago

Script Assertion or Groovy Test step when working with Request Output

I have an output that contains 10's of responses. <e> <RateFactor>0.085607481788467374</RateFactor> <MinAmount>50001.0</MinAmount> <MaxAmount>150000.0</MaxAmount> <Grade>8</Grade> <Eol>$/...
nmrao's avatar
nmrao
Champion Level 3
I did not understand the core issue.

However, I would like to clarify the following:

1. Script Assertion can be used to validate the current test step response for all request types such as HTTP, JDBC, SOAP, REST etc.,

2. Or course, the same above can be achieved using a separate Groovy Test step, but it will be an additional step which can be avoided.

However, there can be other cases where user might want to generate some data or compute / process some data and that is not directly involves on any previous test step.
sprice090161's avatar
sprice090161
Contributor
7 years ago

There are two issues.

1. How to programatically queue the output  responses of the REST service test step?

2. Should it be contained in a groovy test step or in a script assertion?

 

1. I watch some basic groovy tutorials and tried to implement the code, but I think that one must be aware, of how to code in soapui, given the soapui api and wrappers. I sence that some core groovy can't be run directly from a groovy test step. However I'm unclear on this.

 

I opened a ticket and recieved help on configuring a datasource instead, which works great!

 

2. I beleive that there are differences executing a script from a Groovy Test Step vs, a script assertion. Some releated to scope, and other related to capturing the state of an assertion.

 

Thats what I was trying to ask...maybe poorly. :-)