Forum Discussion
SmartBear_Suppo
Alumni
12 years agoHi,
I agree, I'm not sure why the result would encode the tags as < and > in a load test.
No, not for this scenario. There is something similar for endpoints at File -> Preferences -> HTTP Settings, Pre-encoded Endpoints.
The best approach may be to capture the actual value and compare via a groovy assertion.
Using XMLHolder can do this:
http://testautomationnoob.blogspot.com/ ... older.html
Regards,
Marcus
SmartBear Support
1. My assertion is that SoapUI should by default provide a consistent interface for assertion processing regardless of whether the test step is being used in the normal or the load environment.
I agree, I'm not sure why the result would encode the tags as < and > in a load test.
2. Is there a configuration option to enforce such consistency?
No, not for this scenario. There is something similar for endpoints at File -> Preferences -> HTTP Settings, Pre-encoded Endpoints.
3. If the above does not exist, what do you suggest as the best approach for new test assertions and for revisiting existing test projects? I am aware of the CDATA removal Event Handler option that is documented on the soapui.org website.
The best approach may be to capture the actual value and compare via a groovy assertion.
Using XMLHolder can do this:
http://testautomationnoob.blogspot.com/ ... older.html
Regards,
Marcus
SmartBear Support