Hello,
I scheduled a test recently which consists of a simple login test for an application with a 14 minute wait after the test is completed. I then add this test to multiple additional tests as a "test as step". This allows me to repeatedly loop through my login test so I can have it run approximately every 15 minutes for serveral hours on a single schedule. Works great except that my test hung recently. On hitting a linkbutton a javascript confirm box is displayed. Unfortunately the confirm box was made unavailable as it was removed from the foreground by an errant click. This hung the test which did send out a failure message via script I have in the OnAfterTestCompleted event. However the test never seems to have really ended causing multiple scheduled tests to back up and not be executed. What I am wondering is when a test hangs like this how can I detect it, close the browser window and allow subsequent tests to execute? Please let me know if you would like more information or clarifications.
Thanks in advance,
Nick
I scheduled a test recently which consists of a simple login test for an application with a 14 minute wait after the test is completed. I then add this test to multiple additional tests as a "test as step". This allows me to repeatedly loop through my login test so I can have it run approximately every 15 minutes for serveral hours on a single schedule. Works great except that my test hung recently. On hitting a linkbutton a javascript confirm box is displayed. Unfortunately the confirm box was made unavailable as it was removed from the foreground by an errant click. This hung the test which did send out a failure message via script I have in the OnAfterTestCompleted event. However the test never seems to have really ended causing multiple scheduled tests to back up and not be executed. What I am wondering is when a test hangs like this how can I detect it, close the browser window and allow subsequent tests to execute? Please let me know if you would like more information or clarifications.
Thanks in advance,
Nick
3 Answers, 1 is accepted
0
Hi Nick,
I'm not sure I understand how the test is "hung". If an unexpected javascript box appears and cannot be handled I expect the test to simply fail and the TestList to move on to the next test.
Please elaborate on how the test gets hung.
Kind regards,
Stoich
the Telerik team
I'm not sure I understand how the test is "hung". If an unexpected javascript box appears and cannot be handled I expect the test to simply fail and the TestList to move on to the next test.
Please elaborate on how the test gets hung.
Kind regards,
Stoich
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Some
Top achievements
Rank 1
Rank 1
answered on 11 Nov 2011, 10:07 PM
Stoich,
There was a browser issue which would cause the javascript confirm box to be moved out of the foreground. Dont ask me how but it would literally be moved out of the foreground about a half of a second after appearing. It was resolved by clearing the cache. The confirm box was still there. That is how I found the test about 3 days later. I clicked to bring the confirm box to the foreground and clicked ok. At that point I am trying to remember if the test then failed or if it resumed running. I have encountered the same situation on other occassions I believe that a active unlocked rdp session may not have been present but dont remember exactly.
I apologize for being so vague it has just been a while since I have seen it happen and usually dont pay that much attention to it aside from clearing things out to prevent further tests from being held up.
Thanks,
Nick
There was a browser issue which would cause the javascript confirm box to be moved out of the foreground. Dont ask me how but it would literally be moved out of the foreground about a half of a second after appearing. It was resolved by clearing the cache. The confirm box was still there. That is how I found the test about 3 days later. I clicked to bring the confirm box to the foreground and clicked ok. At that point I am trying to remember if the test then failed or if it resumed running. I have encountered the same situation on other occassions I believe that a active unlocked rdp session may not have been present but dont remember exactly.
I apologize for being so vague it has just been a while since I have seen it happen and usually dont pay that much attention to it aside from clearing things out to prevent further tests from being held up.
Thanks,
Nick
0
Hi Nick,
you shouldn't run tests on a locked desktop. Any test that requires moving the mouse or sending keystrokes requires an unlocked desktop (especially so with Silverlight tests).
Telerik tests are not the only ones affected by this Windows limitation. You will find this is a general problem with any tool that performs UI testing. Our tests against HTML based web applications frequently can work on a locked machine because most test steps don't use the mouse or keyboard. Instead they are able to inject a Click or Select events against the element in question (e.g. a button or drop down select). Unfortunately Silverlight doesn't allow us to inject these events. We have to simulate system wide mouse moves and mouse clicks instead. Some of our customers report success using a VNC type of product.
That being said I will need more specific info in order to troubleshoot the problem. Would you be able to send us a test that demonstrates the issue? Keep in mind that the test will have to run against a publicly accessible URL so that we may run it.
Greetings,
Stoich
the Telerik team
you shouldn't run tests on a locked desktop. Any test that requires moving the mouse or sending keystrokes requires an unlocked desktop (especially so with Silverlight tests).
Telerik tests are not the only ones affected by this Windows limitation. You will find this is a general problem with any tool that performs UI testing. Our tests against HTML based web applications frequently can work on a locked machine because most test steps don't use the mouse or keyboard. Instead they are able to inject a Click or Select events against the element in question (e.g. a button or drop down select). Unfortunately Silverlight doesn't allow us to inject these events. We have to simulate system wide mouse moves and mouse clicks instead. Some of our customers report success using a VNC type of product.
That being said I will need more specific info in order to troubleshoot the problem. Would you be able to send us a test that demonstrates the issue? Keep in mind that the test will have to run against a publicly accessible URL so that we may run it.
Greetings,
Stoich
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items