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
SmartBear_Suppo
Alumni
AlumniHi!
ok.. then I don't know what could be filling up memory.. usually soapUI loads the underlying WSDLs the first time a request is made, these will always remain in memory and can take up quite a lot.. I would need to run your project under a profiler to give better answers.
We have done quite a lot of profiling ourselves to see that nothing is lying around in memory, but you could definitely have some setup that we missed.. so if you can share that would be great! Maybe a local mock-service for dummy results (running in another soapUI instance) would be enough to reproduce this !?
regards!
/Ole
eviware.com
ok.. then I don't know what could be filling up memory.. usually soapUI loads the underlying WSDLs the first time a request is made, these will always remain in memory and can take up quite a lot.. I would need to run your project under a profiler to give better answers.
We have done quite a lot of profiling ourselves to see that nothing is lying around in memory, but you could definitely have some setup that we missed.. so if you can share that would be great! Maybe a local mock-service for dummy results (running in another soapUI instance) would be enough to reproduce this !?
regards!
/Ole
eviware.com