ZAPTEST causes possible memory leak

[Curtis DonParticipant]

Hello Zap,

We use ZAPTEST teh Standalone version for some time, and we’ve noticed if we add and run multiple "RunTest" commands in our tests ZAPTEST shows an error "Out of memory" – Why is that and how can we prevent this from happening?

Thanks.

[Sasha ZAPModerator]

Hello CurtisDo,

Thank-you for your question.

Basically a memory leak will happen if a machine’s memory is not getting freed and just getting consumed more and more until there is no memory left for running specific app (In our case this will be the ZAPTEST app).
Basically all ZAPTEST methodscommands free the memory they’ve occupied for temporary use, if a memory leak occurs, because other apps run in a standard machine (In the background, for example) therefore there may be number of reasons for this memory leak to occur.
It is possible that when you run a ZAPTEST based test with a lot of RunTest calls in it, the actual apps (Or their business processes) that are being triggered do not free the memory they are using mostly because they are remain open when the next RunTest calls them (So multiple instances of similar business process will be using memory):
Therefore it is recommended to use as little as possible with the RunTest command and make sure each appbusiness process will be ended before the execution of the next one.

Please contact Zap for further help.

Thanks,
Sasha

[Author]

Posts