I have a test the goes through and cleans-up all the data I generated during my testing. Deleting test users and accounts is a major part of this. I have these tests scheduled to run overnight so we get our results first thing in the morning. The test run however gets to the delete user part and fails to handle the dialog. One would think after the wait time experiences and the element is still not found the test would fail that case and move on. This is not what is happening.
When I come in in the morning and launch the execution machine the test is just chilling with the Dialog on screen. When I manually click it the test continues. I then have to wait for the entire schedule queue to process before I can schedule another run to try and debug it.
On top of this when I get my results email it tells me 0 of 0 tests run. But I just watched a bunch of them run. All the tests in queue have the same results even though I am watching them run.
Seems like there is a bug in the execution server that does not end and fail a test after the time to find or interact has passed. Also another bug where when a scheduled test does not run when it was scheduled and eventually runs when it comes up in the queue why are the results saying 0 of 0 run when you can plainly see they did run. If you are queing scheduled runs then the results of the run regardless of the time should be accurate and meaningful.
When I come in in the morning and launch the execution machine the test is just chilling with the Dialog on screen. When I manually click it the test continues. I then have to wait for the entire schedule queue to process before I can schedule another run to try and debug it.
On top of this when I get my results email it tells me 0 of 0 tests run. But I just watched a bunch of them run. All the tests in queue have the same results even though I am watching them run.
Seems like there is a bug in the execution server that does not end and fail a test after the time to find or interact has passed. Also another bug where when a scheduled test does not run when it was scheduled and eventually runs when it comes up in the queue why are the results saying 0 of 0 run when you can plainly see they did run. If you are queing scheduled runs then the results of the run regardless of the time should be accurate and meaningful.
7 Answers, 1 is accepted
0
Hi Leonard,
I am sorry to hear you are running into problems. Let's focus on the test getting stuck at the dialog. While I can't explain "0 of 0 tests run" it sounds like a domino effect to me. if we can solve the first problem, I expect this second problem will no longer exist.
I have a few questions I need to ask:
Cody
Telerik
I am sorry to hear you are running into problems. Let's focus on the test getting stuck at the dialog. While I can't explain "0 of 0 tests run" it sounds like a domino effect to me. if we can solve the first problem, I expect this second problem will no longer exist.
I have a few questions I need to ask:
- Does this problem always happen, can you make it happen in the day while you're watching it run, or does the test only get stuck running it overnight when you're not looking at the screen?
- What type of dialog is this? There are many dialogs. Some are modal, some are actual separate windows while others look like windows but actually appear in the browser window and are part of the HTML. A screen shot of the problem dialog will help us understand what you're dealing with.
- How is your script currently setup to try and handle this dialog? A non-coded step, what is it? Or are you using code? What is that code?
We need this information before deciding the next step.
Regards,Cody
Telerik
0
LEONARD
Top achievements
Rank 1
Rank 1
answered on 26 Mar 2014, 05:46 PM
1. It does not hang when I am watching the run just overnight when the test runs. I know that we require an active session in order to perform mouse and keyboard interaction but I would think if the session were not active the wait period for running a test case would have lapsed and the test would have ended and that test case failed.
2. Attached screenshot of Dialog opened.
3. It is a non coded step using test studios handle dialog functionality. Attached is the step in the test and its properties.
2. Attached screenshot of Dialog opened.
3. It is a non coded step using test studios handle dialog functionality. Attached is the step in the test and its properties.
0
Hello Leonard,
...but I would think if the session were not active the wait period for running a test case would have lapsed and the test would have ended and that test case failed.
You should have gotten an error message during test initialization. Our dialog monitoring code should have failed because it would be unable to get a handle to an "active desktop" in order for it to even start monitoring popup dialogs. We usually see the test failing before it even got started.
I don't recognize the window style for the screen shot of the popup you have shown. Looks like you're running Windows 8 or 8.1, correct? That actually could be the difference. We know what Windows 7 and below does on a locked machine, but we don't know what Windows 8 does in the locked state. This is something I'll have to test. Which version of IE are you using?
Regards,
Cody
Telerik
...but I would think if the session were not active the wait period for running a test case would have lapsed and the test would have ended and that test case failed.
You should have gotten an error message during test initialization. Our dialog monitoring code should have failed because it would be unable to get a handle to an "active desktop" in order for it to even start monitoring popup dialogs. We usually see the test failing before it even got started.
I don't recognize the window style for the screen shot of the popup you have shown. Looks like you're running Windows 8 or 8.1, correct? That actually could be the difference. We know what Windows 7 and below does on a locked machine, but we don't know what Windows 8 does in the locked state. This is something I'll have to test. Which version of IE are you using?
Regards,
Cody
Telerik
0
LEONARD
Top achievements
Rank 1
Rank 1
answered on 27 Mar 2014, 03:00 PM
We are running our Execution on Windows Server 2012 R2 Standard on IE 11.0.9600.16521.
0
Hello Leonard,
I have reproduced the problem. The only real solution however is to leave the machine in an unlocked state. We can fix the test getting stuck when the dialog appears, but the test will still fail when the machine is locked.
Regards,
Cody
Telerik
I have reproduced the problem. The only real solution however is to leave the machine in an unlocked state. We can fix the test getting stuck when the dialog appears, but the test will still fail when the machine is locked.
Regards,
Cody
Telerik
0
LEONARD
Top achievements
Rank 1
Rank 1
answered on 29 Mar 2014, 07:04 PM
Thanks Cody. I'm working with my IT department to edit the group policy on our test machines to stay on. They are also assess some of the suggestions given in the documentation pages. If all else fails I found a program that will press the f15 key at a programmable interval say every 5 minutes. This supposedly will keep it awake and active and since no keyboard has an f15 key its a reasonable sounding option.
0
Hi Leonard,
What works well for us is Microsoft's Hyper-V. I make a connection to the VM using Hyper-V manager and the OS can't tell the difference between that connection and a real graphics adapter (unlike remote desktop connections). The VM is set to never lock, never enter screen saver, but I must enter my domain credentials before Hyper-V allows me to connect. Mouse and Keyboard and Dialogs work in this environment. I believe VMWare has something similar that works the same way, but I've never used it since we don't have it.
Regards,
Cody
Telerik
What works well for us is Microsoft's Hyper-V. I make a connection to the VM using Hyper-V manager and the OS can't tell the difference between that connection and a real graphics adapter (unlike remote desktop connections). The VM is set to never lock, never enter screen saver, but I must enter my domain credentials before Hyper-V allows me to connect. Mouse and Keyboard and Dialogs work in this environment. I believe VMWare has something similar that works the same way, but I've never used it since we don't have it.
Regards,
Cody
Telerik