Internet Explorer "Wait for condition has timed out" on Windows 8.1 x64

7 posts, 0 answers
  1. James
    James avatar
    8 posts
    Member since:
    Feb 2014

    Posted 01 Mar 2014 Link to this post

    I am trying to test my application on Windows 8.1 x64 and I always get a timeout when trying to use the command LaunchNewBrowser to open Internet Explorer 11. Basically it opens the browser window but it sits at the about:blank screen and never goes anywhere until I get the timeout message from my app. The windows 8.1 machine is running on VMWare Workstation and has no extra software installed except from windows update. I installed windows 8.1, installed all critical and recommended updates until nothing was left (multiple reboots). I then installed the same telerik testing framework msi installer that I used on my development machine. I don't even have adobe reader or antivirus or ANYTHING else on this box, it is very clean! The same code runs fine on my windows 7 x64 box and I don't recall doing anything special to get set up. I have been up and down these forums trying everything and here is a summary of what I have done:

    -Disabled protected mode for all zones
    -Completely disabled UAC
    -Disabled the popup blocker
    -Added the url I want to visit to trusted sites
    -Disabled 3rd party addons
    -Repaired the install of Testing Framework using the same installer
    -Rebooted multiple times between all of these tests

    I was getting so frustrated that I installed chrome, enabled the telerik extension and ran the same test with chrome AND IT WORKED!

    Does the newest most updated version of Internet Explorer not work with the testing framework on Windows 8.1? This is such an unadulterated box that I can't believe it doesn't work after all of this. Please help!
  2. Bill
    Bill avatar
    2 posts
    Member since:
    Mar 2014

    Posted 02 Mar 2014 in reply to James Link to this post

    I had the same problem on a Windows 8.1 laptop and moved the project over to a Windows 7 laptop and IE worked fine.
  3. James
    James avatar
    8 posts
    Member since:
    Feb 2014

    Posted 02 Mar 2014 Link to this post

    yes, i can confirm that the exact same code works fine on windows 7. I haven't yet been able to test windows 8 (without 8.1) nor have I yet tried downgrading IE to v10 to see if it somehow has something to do with the newest version of ie 11 on windows 8 (which I can confirm is slightly different than ie 11 for windows 7: http://stackoverflow.com/questions/18083239/what-happened-to-always-refresh-from-server-in-ie11-developer-tools). I will see if I can find time to do these tests at some point but I am a little miffed that this isn't working on a brand new windows 8.1 machine out of the box, but then again it is free....
  4. Boyan Boev
    Admin
    Boyan Boev avatar
    1040 posts

    Posted 06 Mar 2014 Link to this post

    Hello James,

    Could you please go ahead and download our latest internal version of Testing Framework (1417).

    Give that a try and let us know the result.

    Hope to hear from you soon.

    Regards,
    Boyan Boev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  5. Bill
    Bill avatar
    2 posts
    Member since:
    Mar 2014

    Posted 06 Mar 2014 in reply to Boyan Boev Link to this post

    I resolved this issue by search through other posts. You need to run VS  as "Run as administrator" for it work even if you are administrator on the workstation. That resolved my IE timeout issue.
  6. James
    James avatar
    8 posts
    Member since:
    Feb 2014

    Posted 07 Mar 2014 Link to this post

    @Boyan: I attempted to find an internal version of the Testing Framework (1417) but I cannot find a download link. Can you send me the direct link or at least instructions on how I can find it?

    @Bill: I do not have my development tools installed on my Windows 8.1 box. I did try right-clicking the exe and choosing 'Run as administrator' but it still gives me the same timeout result as before. I would hate for this to be the answer anyway since it would mean that anyone running these tests would be forced to run as admin every time.
  7. Boyan Boev
    Admin
    Boyan Boev avatar
    1040 posts

    Posted 11 Mar 2014 Link to this post

    Hi James,

    Here is a direct link for the latest internal build of the Testing Framework (1510).

    Let me know if this helps.

    Regards,
    Boyan Boev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
Back to Top