Memory usage with large data driven test
Hi - I am running a data driven test case with about 100 rows of data. It calls 2 other test cases during each loop. It also uses the methods of an external Groovy class, but they are all declared ...
Forum Discussion
thanks.
i know. it's set to 100.
but the problem is that all errors are still saved somewhere. arent they? after i clear the error log i get back huge ammount of memory.
if i have 1.000.000 or more errors (which can happen during night tests) then SoapUI starts having bad time.
i don't need all those errors with more or less details. not even in report, because you can immageine how big it would be.
perhaps you can make option of disabling error log in load test (like soapUI log, http log, script log,...?). it would be a nice feature.
with best regards,
beno
i know. it's set to 100.
but the problem is that all errors are still saved somewhere. arent they? after i clear the error log i get back huge ammount of memory.
if i have 1.000.000 or more errors (which can happen during night tests) then SoapUI starts having bad time.
i don't need all those errors with more or less details. not even in report, because you can immageine how big it would be.
perhaps you can make option of disabling error log in load test (like soapUI log, http log, script log,...?). it would be a nice feature.
with best regards,
beno