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>$/EFA</Eol>
<AssetType null="true"/>
<Term>12</Term>
<PaymentFrequency null="true"/>
</e>
I have to use this data to recreate the "RateFactor" in a standalone GUI tool and then compare the two rate factors, asserting that they are equal.
This will require me to either store each instance of the data somewhere, and access it using Selenium from a Groovy script,
Or set up a for/each loop, access the first instance of data, save it to local properties, make the required Selenium calls to enter the data, Get the result, and then compare the new result, with the stored result.
Repeat for each instance o fht edata in the output.
My Question:
Can I do all of this in the Script assertion or am I limited to only accessing the response data and not Selenium?
Conversly, If I create a Groovy Test Step, can I access the response data itteretively, and how would I do that ?
So I'm asking the limitations of the two scripting options.