I have been experiencing an issue where the first test in my test list will fail to execute and we can find no reason for it to do so. We have built a Buffer Test and added it to all our test lists which simply connects to the browser waits for 1 minute then maximizes the browser. Even this simple test will fail but it allows us to get the real test to run. We are running all our test lists in IE11 if that means anything. Is there a setting or some other best practice we should use to allow are test list to run and the first test to execute properly?
3 Answers, 1 is accepted
0
Hi Sean,
Before we can begin to suggest a fix we need to understand what is causing the failure. Please let the first test fail then go to Step Failure Details, find and click Export then attach the generated .zip file. It contains valuable information we need to diagnose this type of failure.
Regards,
Cody
Telerik
Before we can begin to suggest a fix we need to understand what is causing the failure. Please let the first test fail then go to Step Failure Details, find and click Export then attach the generated .zip file. It contains valuable information we need to diagnose this type of failure.
Regards,
Cody
Telerik
0
Sean
Top achievements
Rank 1
Rank 1
answered on 03 Mar 2015, 04:03 PM
Attached log from failed test.
0
Hi Sean,
Thank you for the test log. Basically it's telling us that Test Studio timed out trying to connect to the browser. It makes no sense why this would only happen on the first test in the test list. Test Studio doesn't do anything different for the first test in the list then the rest of the tests in the list. I'm trying to think what could possibly cause this behavior. Also to answer your original inquiry no there is no "setting or some other best practice we should use to allow are test list to run and the first test to execute properly".
How long does it take for IE to launch on this computer? I wonder if it's just slow loading the first time and is fast the second time it loads. If this theory is valid I recommend searching for ways to make IE run faster, or make Windows load applications faster (IE is just another application).
Regards,
Cody
Telerik
Thank you for the test log. Basically it's telling us that Test Studio timed out trying to connect to the browser. It makes no sense why this would only happen on the first test in the test list. Test Studio doesn't do anything different for the first test in the list then the rest of the tests in the list. I'm trying to think what could possibly cause this behavior. Also to answer your original inquiry no there is no "setting or some other best practice we should use to allow are test list to run and the first test to execute properly".
How long does it take for IE to launch on this computer? I wonder if it's just slow loading the first time and is fast the second time it loads. If this theory is valid I recommend searching for ways to make IE run faster, or make Windows load applications faster (IE is just another application).
Regards,
Cody
Telerik