IE8: Download Dialog issues with Data Driven tests

[John]

In IE8 with all settings configured as per the Telerik documentation.
* i.e. the 'Close download when complete' checkbox is UNCHECKED.

* The ReuseAppWindow property of the test is set to 1.

I am running a test that logs into and navigates a site using Local Data. The final step includes downloading a file.

The first iteration of the test, using the first row of Local Data, executes perfectly: the download dialog is recognized and handled accordingly (the filepath is entered from the Local Data).

The user is then logged out, the cookies cleared and a new browser window opened for the next run.

The second iteration of the test makes it to the end then fails to recognize the Windows Dialog as a Download Dialog and executes the 'Unexpected dialog' process instead (which fails the test).

This happens even when the Local Data is EXACTLY THE SAME in both rows.

[Cody]

Hi,

I have confirmed this is a bug in Test Studio. I have filed a bug report on it here. As a temporary work around you can implement 100% in code the dialog handling. I recommend using the DownloadsDialogHandler as shown near the bottom of that page. This will work in your scenario. 

All the best,
Cody
the Telerik team

[Benjamin]

I am experiencing a similar issue. I just upgraded my Test Studio on Wednesday to the 2012.1 release that came out on that day. I am using script step as you mentioned above as I am using variables in the file name when saving from my data source. However, if my test has more than one step using DownloadDialogsHandler, the second and subsequent steps time out and don't download any file at all. But, when I use the Download Dialog Handler from the menu, the script succeeds without error. I also created tests that do not have data binding and the scripted method would fail in the same way while the handler option would succeed as they did with data binding.

[Byron]

Hi Benjamin,

The behavior you mention is due to a design limitation: Test Studio will not handle multiple dialogs of the same type in the same test using the Download Dialog Handler from the Quick Tasks menu.

Your issue could be resolved by using data driven download dialog handlers from the menu and splitting the two dialog handlers into their own tests so that there is only one download dialog handler step in each test. Then, you can combine them using Test as Step or a Test List.

Alternatively if you prefer to stick with your coded approach, you are probably missing a cleanup step in your code. When you are finished using the download dialog in your code, make sure that the dialog handler is removed with code similar to this:

Manager.DialogMonitor.RemoveDialog(dlg);  // dlg is the DownloadDialogsHandler that was previously added

All the best,
Byron
the Telerik team