Hello,
I am newer using Telerik Test Studio. I am facing an error with an iframe in Chrome. Currently I am using Chrome (Version 25.0.1364.152)
and Telerik version 2012.2.1420.0.
This frame has a random id but I defined this object with the following options:
-BaseURL:~/Email2.php
-Id:~WVRANDOMID
-Index:3
-Name:~WVRANDOMID
The error shown is:
Failure Information:
~~~~~~~~~~~~~~~
Element was 'not found'. Criteria: Element 'Exists'.
Waiting for frame '[Frame:id=~WVRANDOMID,name=~WVRANDOMID,src=~/Email2.php,UseQuery:False]' timed out. Error: Wait for condition has timed out
The script is working well in IE8 and FF browser
Could you please help me how solve this issue?
I am newer using Telerik Test Studio. I am facing an error with an iframe in Chrome. Currently I am using Chrome (Version 25.0.1364.152)
and Telerik version 2012.2.1420.0.
This frame has a random id but I defined this object with the following options:
-BaseURL:~/Email2.php
-Id:~WVRANDOMID
-Index:3
-Name:~WVRANDOMID
The error shown is:
Failure Information:
~~~~~~~~~~~~~~~
Element was 'not found'. Criteria: Element 'Exists'.
Waiting for frame '[Frame:id=~WVRANDOMID,name=~WVRANDOMID,src=~/Email2.php,UseQuery:False]' timed out. Error: Wait for condition has timed out
The script is working well in IE8 and FF browser
Could you please help me how solve this issue?
1 Answer, 1 is accepted
0
Hello Ariel,
Thank you for contacting Telerik Support.
Unfortunately I cannot tell exactly why the frame could not be found on playback in Chrome from the info alone. I suspect there may be some small difference with one of these frame properties when it's loaded in Chrome. I suggest manually inspecting the page contents using Chrome developer tools (F12) to locate the frame and compare its properties to those you've provided.
If this suggestion does not help, we will need your help reproducing the problem locally to continue troubleshooting. If allowing us direct access to the app or one which behaves like it is not possible (eg. app is local and/or private), we can instead attempt to "simulate" your app through a captured Fiddler trace which you can also attach to this ticket in a zip. If you are unfamiliar with how to create one, this link will provide you with step-by-step instructions for download and use. Alongside the previous instructions, please make sure to enable the 'Store binaries' and 'Decrypt HTTPS traffic' options prior to starting the capture.
Regards,
Mario
Telerik
Thank you for contacting Telerik Support.
Unfortunately I cannot tell exactly why the frame could not be found on playback in Chrome from the info alone. I suspect there may be some small difference with one of these frame properties when it's loaded in Chrome. I suggest manually inspecting the page contents using Chrome developer tools (F12) to locate the frame and compare its properties to those you've provided.
If this suggestion does not help, we will need your help reproducing the problem locally to continue troubleshooting. If allowing us direct access to the app or one which behaves like it is not possible (eg. app is local and/or private), we can instead attempt to "simulate" your app through a captured Fiddler trace which you can also attach to this ticket in a zip. If you are unfamiliar with how to create one, this link will provide you with step-by-step instructions for download and use. Alongside the previous instructions, please make sure to enable the 'Store binaries' and 'Decrypt HTTPS traffic' options prior to starting the capture.
Regards,
Mario
Telerik