Leave Browser Open after Iteration

Hi Robert,

This is what our "Run To Here" feature was designed for. Give it a try and tell me if it meets your needs.

Regards,
Cody
Telerik

When running a data driven test, I need the browser to stay open at the end of each and every iteration. The "run to" option only runs the first iteration of a data driven test.

Hi Robert,

Hmmm I see. Then what we really need to figure out is what is causing the browser to close in the first place. For a data driven test, the browser is NOT supposed to close between iterations. It's supposed to launch a new browser at the beginning of the test, run all iterations, then close the browser when the test is finished. To try and discover what's going wrong, can you share with me your test and/or entire test project (be sure to point out the problem test and in which step is the browser closing). I'll study it and try to determine what is causing the browser to close.

Regards,
Cody
Telerik

I'm running a test that starts a download in an ActiveX control. Unfortunately, I can't tell whether or not the download is complete, and if the window closes, the download stops. The download is the end of the test (manually verify it's downloaded). I am downloading over 10,000 different items.

Right now, to prevent the test from closing, I have set an execution delay at the end of 2 minutes. There are two issues with this. First, the browser closes in the middle of downloads that take longer than 2 minutes. Second, it does not begin running the next test until the 2 minutes are up, even if the download finishes in 15 seconds (the majority of the files).

By leaving the browser window open and starting a new iteration in a new window, I can leave the browser window open indefinitely, allowing long downloads to complete. I can run 40 iterations at a time (per my other forum post, though this issue is for a different test) then manually close all the windows.

Hello Robert,

I'm running a test that starts a download in an ActiveX control.

I see. That alone does complicate the automation simply because Test Studio cannot directly automate ActiveX controls.

...the browser closes in the middle of downloads that take longer than 2 minutes.

This sounds like the core problem. Do we know why this happens? Under no condition that I can think of should the browser close. It might abort the download, but this should cause the browser to close. Is it possible the ActiveX control is crashing and as a result the browser is closing?

 Is it possible for me to get direct access to your application so I can reproduce this problem, study it and try to come up with a solution? Since you do have a current license of Test Studio, you are welcome to create a new support ticket to pass me this information. Unlike public forum posts (like this one) only you and Telerik support can view the contents of your support tickets.

I can run 40 iterations at a time (per my other forum post, though this issue is for a different test) then manually close all the windows.

I didn't find this other forum post you're referencing. But with this in mind, while it would be a lot more complcated and require some careful programming, it would be possible to open multiple browser windows simultaneously and automate them in parallel.

Regards,
Cody
Telerik

http://www.telerik.com/automated-testing-tools/community/forums/test-studio/general-discussions/data-driven-test.aspx

Is my other forum post. It's a separate issue than this.

I can't give access to my current program and my script is rather simple, but here's some more information.

The files are downloaded INSIDE the ActiveX control, i.e. not using the Browser download whatsoever. That's why I can't set up any verification for it. I initialize the download by doing an off-set click into the ActiveX window, then run coded keyboard commands to navigate through the strange download dialogue box. After that, the download begins and is monitored inside the ActiveX control.

I'm going to try setting up my test as follows and I'll get back to you with my results.

Subtest - Login
-Navigate
-UN / PW
-Submit
Subtest - Get Active X Files - Data Driven - Run 10,000 Times
-Navigate (Data Driven)
-Download
-Open New Browser Tab
Subtest - Delay Forever

Can you see any issues with this setup?

Hello,

Is my other forum post. It's a separate issue than this.

Ah yes, I saw (and responded) to it as well.

These items concern me:

• Run 10,000 Times - You'll create such a large test result set that Test Studio won't be able to handle it. You'll simply run out of memory.
• Open New Browser Tab - Test Studio does not support tabbed browsing in IE. We do support opening additional browser windows however. See Pop-ups Open in a New Window.

Regards,
Cody
Telerik

Thanks!

I'll probably batch the job so that the file doesn't get large enough to crash and use New Windows instead of New Tabs.

Hi,

Sounds good to me. I'll stand by for your results and assist if needed.

Regards,
Cody
Telerik