I have been having trouble with this issue for quite some time now. We have Test Studio's standalone version for QAs running on a server through remote access. 2 QAs including me work on capturing tests using test studio on the server and the server has around 6 gigs of RAM. So, that provides a brief background of infrastructure I am dealing with here.
Now, while running the test cases and especially running them as test lists we face a strange scenario; TEST STUDIO doesn't close the browser after a test case has been run and after 10-15 such instances there are almost 10-15 browsers open (this I saw when I opened the task manager and saw the Processes).
This for some reason clogs the RAM or something and doesn't allow the browser to open when another test case needs to run.
Now, there is an option which says CloseBrower (its a drop down and can be set to true or false). I used this option on the last steps of some of my tests, but even this was not helpful.
So, what I am saying here is - Is there some option to forcefully close the browser after the test case is completed?
KUMAR
Now, while running the test cases and especially running them as test lists we face a strange scenario; TEST STUDIO doesn't close the browser after a test case has been run and after 10-15 such instances there are almost 10-15 browsers open (this I saw when I opened the task manager and saw the Processes).
This for some reason clogs the RAM or something and doesn't allow the browser to open when another test case needs to run.
Now, there is an option which says CloseBrower (its a drop down and can be set to true or false). I used this option on the last steps of some of my tests, but even this was not helpful.
So, what I am saying here is - Is there some option to forcefully close the browser after the test case is completed?
KUMAR