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 again!
the latest nightly build adds a "Discard Response" property (bottom left) to all request-teststeps; setting this to true will remove the saved response from memory after the teststep has executed (and asserted itself) unless the corresponding editor is open in which case the response will be kept in memory (so it can be shown in the editor).
Try setting this to true for teststeps whose response you are not using in any subsequent steps (for example in property transfers, script access, etc), this might make quite a difference in your case.
If you can not use this since you need to keep the response in memory for some reason, you could add a script step that removes the response when it is not needed any more;
testRunner.testCase.testSteps["..."].testRequest.setResponse( null, context )
regards,
/Ole
eviware.com
the latest nightly build adds a "Discard Response" property (bottom left) to all request-teststeps; setting this to true will remove the saved response from memory after the teststep has executed (and asserted itself) unless the corresponding editor is open in which case the response will be kept in memory (so it can be shown in the editor).
Try setting this to true for teststeps whose response you are not using in any subsequent steps (for example in property transfers, script access, etc), this might make quite a difference in your case.
If you can not use this since you need to keep the response in memory for some reason, you could add a script step that removes the response when it is not needed any more;
testRunner.testCase.testSteps["..."].testRequest.setResponse( null, context )
regards,
/Ole
eviware.com