Completed
Last Updated: 23 Apr 2014 05:17 by ADMIN
ADMIN
Cody
Created on: 18 Jun 2013 18:36
Type: Bug Report
2
Be able to have long running tests
There are a few valid instance where customers need to create very long running tests, tests that require hours to execute. Currently Test Studio struggles to handle these due to having to log and maintain the results in memory. The longer the test runs, the more memory that is consumed to hold the results. It would be useful if Test Studio didn't require so much memory for the log/results for these long running tests.
3 comments
ADMIN
Iliyan Panchev
Posted on: 22 Apr 2014 08:10
If there are still problems, this article may help - http://docs.telerik.com/teststudio/user-guide/knowledge-base/oom.aspx
ADMIN
Iliyan Panchev
Posted on: 22 Apr 2014 07:48
There are a lot of optimizations in that area in the past year, so this shouldn't be a problem anymore.
ADMIN
Konstantin Petkov
Posted on: 10 Jul 2013 13:33
Hello,

Sure it takes memory to keep objects runtime, however it really depends on how big these objects are.

The objects that I'm aware of taking significant amount of memory are the test failure details - Test Studio used to keep the image and DOM in time of failure in memory. However, since 2012.2.1204 that has been addressed by saving the data on disk during the entire run (then cleaning up the local files as soon as the run completes).

Another option that helps generally is related to the RecycleBrowser setting. If turned on this guy will keep the same browser open during the entire run. If the application causes memory consumption in the browser process then switching that off should definitely help. Each test will launch new browser and have the previous browser closed (and it's process memory released).

I hope this helps!