Dear Telerik support-team,
We run our TestLists remotely on virtual machines.
The TestList succeeds only when I have a remote connection opened and when my mouse is also focussd on the remote desktop screen.
When I run it remotely without having the virtual machine open on my desktop (remote desktop is minimized at that moment), the test fails at the standard "Handle 'Download' Dialog". It is not able to correctly handle this dialog. We have the latest version of Test Studio and it should be able to handle these dialogs better than before..
Is this a known issue? And how can this be solved?
Thanks for answering.
We run our TestLists remotely on virtual machines.
The TestList succeeds only when I have a remote connection opened and when my mouse is also focussd on the remote desktop screen.
When I run it remotely without having the virtual machine open on my desktop (remote desktop is minimized at that moment), the test fails at the standard "Handle 'Download' Dialog". It is not able to correctly handle this dialog. We have the latest version of Test Studio and it should be able to handle these dialogs better than before..
'13-1-2014 13:05:08' - 'Pass' : 7. Click 'JaIkWilDeLink''13-1-2014 13:05:34' - 'Fail' : 8. Handle 'Download' dialog.------------------------------------------------------------Failure Information: ~~~~~~~~~~~~~~~Timed out waiting '25000' msec. for download dialog to be handled.InnerException:System.TimeoutException: Timed out waiting '25000' msec. for download dialog to be handled. at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.DownloadDialogHandlerDescriptor.Execute(Browser browser) at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.DialogHandlerDescriptor.Execute(IAutomationHost browser) at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteStep(Int32 order)------------------------------------------------------------'13-1-2014 13:05:34' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.Is this a known issue? And how can this be solved?
Thanks for answering.
4 Answers, 1 is accepted
0
Reinout
Top achievements
Rank 2
Rank 2
answered on 14 Jan 2014, 07:30 AM
With the trick from the "Keep an Active Session Running on the Execution Server", this problem seems to be solved.
------------------------------------------------------
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/knowledge-base/scheduling/keep-an-active-session.aspx
------------------------------------------------------
- Prepare three machines, virtual or physical. One of these is your intended execution server. Let's call the three machines A, B and C. Let's say B is the intended Execution Server.
- Start a Remote Desktop Connection on machine C and use it to log into A.
- Once logged in, start a Remote Desktop Connection on A and use it to connect to B.
- Once logged into B, remove the Remote Desktop Connection between A and C.
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/knowledge-base/scheduling/keep-an-active-session.aspx
0
Hello Reinout,
Thank you for contacting us.
You are absolutely correct, any test that requires moving the mouse or sending keystrokes requires an unlocked desktop/active session.
We are glad to hear that you have resolved the issue.
If you need any additional assistance, please do not hesitate to contact us again.
Regards,
Boyan Boev
Telerik
Thank you for contacting us.
You are absolutely correct, any test that requires moving the mouse or sending keystrokes requires an unlocked desktop/active session.
We are glad to hear that you have resolved the issue.
If you need any additional assistance, please do not hesitate to contact us again.
Regards,
Boyan Boev
Telerik
0
Reinout
Top achievements
Rank 2
Rank 2
answered on 21 Jan 2014, 08:14 AM
Still with this setup connected I get more errors running a test list on my remote machine in comparison to my local machine.
Four problems that occurred:
1) After continuing to a new page, elements are not found (it seems that clicking a next button, to load the new page, fails)
2) Handle download dialogs fail randomly
3) When navigating to a new URL, we get a IE warning message (stay or leave the page), we use the Onbeforeunload handler to solve this. This works locally but fails remotely.
4) When I run a testlist remotely, is it using TFS to upload the scripts, or my local versions of scripts?
Do you have some insights in these four problems running our tests remotely?
Four problems that occurred:
1) After continuing to a new page, elements are not found (it seems that clicking a next button, to load the new page, fails)
2) Handle download dialogs fail randomly
3) When navigating to a new URL, we get a IE warning message (stay or leave the page), we use the Onbeforeunload handler to solve this. This works locally but fails remotely.
4) When I run a testlist remotely, is it using TFS to upload the scripts, or my local versions of scripts?
Do you have some insights in these four problems running our tests remotely?
0
Hi Reinout,
The test list execution is much faster than the quick execution.
You can try several options.
1. Put some wait for exists steps for the element that Test Studio cannot find.
2. You can put some execution delay in the test list settings (see the attached screen shot).
3. You can also try to use 2 Test List properties which can potentially help you not getting a not responding browser - in Test List settings, Edit Settings, Web tab - KillBrowserProcessOnClose and RecycleBrowser. Try turning each of them on to see if this will help your execution - these options are to forcibly kill all browser processes when a test finishes and to reuse the browser window and not start a new browser for every test, which in your case with slow loading of the test application might help.
4. We are releasing an official service pack for Test Studio next week (probably on Monday) which contains many bug fixes and improvements. Please install it and give it a try.
Hope this helps.
Regards,
Boyan Boev
Telerik
The test list execution is much faster than the quick execution.
You can try several options.
1. Put some wait for exists steps for the element that Test Studio cannot find.
2. You can put some execution delay in the test list settings (see the attached screen shot).
3. You can also try to use 2 Test List properties which can potentially help you not getting a not responding browser - in Test List settings, Edit Settings, Web tab - KillBrowserProcessOnClose and RecycleBrowser. Try turning each of them on to see if this will help your execution - these options are to forcibly kill all browser processes when a test finishes and to reuse the browser window and not start a new browser for every test, which in your case with slow loading of the test application might help.
4. We are releasing an official service pack for Test Studio next week (probably on Monday) which contains many bug fixes and improvements. Please install it and give it a try.
Hope this helps.
Regards,
Boyan Boev
Telerik