FileUploadDialog not handled if no user logged interactively.

[Alexey Shcherbak]

Another issue appeared: FileUploadDialog  cannot be handled if test executed in non-interactive environment.
We have console app test scenario, which pop-up FileUpload dialog. During debug and interactive checks this dialog was handled successfully by this code:

var fileDialog = new FileUploadDialog(ab, toAbsPath(testImage), DialogButton.OPEN);
mgr.DialogMonitor.AddDialog(fileDialog);
mgr.DialogMonitor.Start();

But when we deployed it on our monitoring server (win2003EE SP2 \ IE8) - this code no longer works. Console app periodicaly started by special monitoring software - its run in interactive but always LOCKED session (Its like you scheduled program to run with custom app and locked your PC). After few runs I logged in and saw all instances of IE, not closed and with FileUploadDialog popped (and not handled properly).
I tried to figure this bug origin with Sysinternals procmon but was unable to deal with all that calls ( saved dump btw).
Any ideas or help how to track and fix that misbehaviour.

UPDATE: I read anwer on this topic
http://www.telerik.com/automated-testing-tools/community/forums/webui-test-studio-developer-edition/webaii-automation-framework/simulated-clicks-not-running-if-machine-is-in-locked-state.aspx
but i still wonder why then all other my tests run fine, except with FileUploadDialog.
I suspect this is because FileUploadDialog is win32 window, not browser one, but then can you point me to working example of FileUpload scenario without this dialog monitoring ( one in docs doesn't work, afaik).

[Cody]

Hello Alexey Shcherbak,

You have run into one of the roadblocks of UI automation. A WebAii test can work find so long as it doesn't do any simulated keystrokes/typing or actually moving of the mouse. We try hard to make the automation work as much as possible using direct DOM manipulation (i.e. working with the HTML loaded in the browser and talking to the browser). Unfortunately, as you have discovered, the File Upload dialog is a Win32 window, not an IE window. Thus we have to treat it different and yes it does require full interactive desktop to be able to handle it. There's no work around for this. it is a Windows limitation for UI actions.

Regards,
Cody
the Telerik team

[Alexey Shcherbak]

Thanks for your explanation. It would be pretty unnessesary, at least  FileUploadDialog itself, when HtmlInputFile.Upload() will work correctly  ;)