Forum Discussion
SmartBear_Suppo
Alumni
16 years agoHi Radgon,
thanks for this, I think I understand it now :-)
The problem is that each time the generator triggers the soapUI Runner, it starts a whole new run of the soapUI TestCase, resulting in new requests from the beginning of your DataSource each time. I suggest you break out the reading of the data-source into a custom component in loadUI and then use it to parameterize the soapUI TestCase which would contain only a request; I've described this approach in a blog entry available at http://www.eviware.com/blog/?p=104, please check it out and let me know if it makes sense to you.
regards!
/Ole
eviware.com
thanks for this, I think I understand it now :-)
The problem is that each time the generator triggers the soapUI Runner, it starts a whole new run of the soapUI TestCase, resulting in new requests from the beginning of your DataSource each time. I suggest you break out the reading of the data-source into a custom component in loadUI and then use it to parameterize the soapUI TestCase which would contain only a request; I've described this approach in a blog entry available at http://www.eviware.com/blog/?p=104, please check it out and let me know if it makes sense to you.
regards!
/Ole
eviware.com