Forum Discussion

fayrehouse's avatar
fayrehouse
Frequent Contributor
11 years ago

Chrome 29 / IE 9.0 / FF24

Hi all,



Currently evaluating TC for our purposes. We have 9.31.3889.7, and Chrome 29 / IE 9.0.8112.16421



Trying a very simple test - keyword test, runbrowser/chrome/ourtesturl fails to start Chrome.



Similarly if I change the browser to IE, TC can start the browser, but fails to navigate to the URL - I even tried adding a separate "navigate" step - no joy.



Running against Firefox 23.0.1 is no problem, but an upgrade to FF 24 did not work.



I notice the latest supported build of Chrome for TC is 28... 



Can we expect a patch for these browser issues soon?

9 Replies

  • Sorry Ignore this! I accidently posted. 

    Please delete if possible. 



  • fayrehouse's avatar
    fayrehouse
    Frequent Contributor
    Thanks Kim - the FF24 hook dll was certainly what was needed, and FF now seems functional again.



    However, problems persist in Chrome and IE - but I'm not necessarily convinced that it is purely a problem with TC....



    Trying to start Chrome with TC doesn't even start Chrome, let alone navigate to the specified page.



    Trying to start IE with TC starts IE, but doesn't navigate - the reason I don't think it's a TC fault is that I've rolled IE back to IE8 - and the problem persists... and I suspect SmartBear would have got TC working with IE8 by now ;-) 



    BTW I'm sure Chrome was only listed as supported up to 28 on the Smartbear site earlier ;-)



    Any other pointers as to what might be the problem?
  • fayrehouse's avatar
    fayrehouse
    Frequent Contributor
    Ok, Chrome problem cause identified - reason for problem unknown.



    With no Chrome window present, I have about 6-7 Chrome.exe processes listed in Task Manager! Seemingly TC is trying to connect to one of these "rogue" processes, and as such, getting nowhere!



    If I kill these processes manually, and run my simple test - it's fine!



    Can anyone suggest why Chrome is creating so many processes, and then leaving most of them behind on exit?



    Also, still no closer with IE ...



  • I think i'm right in saying that Chrome creates a process for every extension or tab etc you have... 

    You may have to run a script at the end of your test to ensure its processes are killed using Terminate()



    http://support.smartbear.com/viewarticle/30751/



    maybe something like:



    if(Sys.WaitBrowser().Exists)

      {


      Aliases.browser.Terminate();


      }


      

    (asuming you're using name mapping/aliases).





    Also you may find the following useful if you've not already seen them. They are articles about preparing the different web browsers before testing. 



    http://support.smartbear.com/viewarticle/26786/



    Hope this helps =)









  • Also did TC give you any errors inthe Test log when it failed to navigate to the page?

    Maybe a screen shot of your test? 
  • fayrehouse's avatar
    fayrehouse
    Frequent Contributor
    Thanks Kim,



    Chrome issue also now resolved.... There's a setting in Chrome - settings/Advanced Settings/Continue running background apps when Google Chrome is closed



    Turn that off, and all is well.



    Still can't get IE resolved tho - no error image - since there is no error reported - TC claims to have successfully navigated - but it most certainly hasn't!





    #verystrange



    :)



  • fayrehouse's avatar
    fayrehouse
    Frequent Contributor
    Latest update:



    Available browsers on my machine:




    Browser 0 : Mozilla Firefox ver.24.0.0 (x86)


    Browser 1 : Microsoft Internet Explorer ver.8.0.7601.17514 (x86)


    Browser 2 : Microsoft Internet Explorer ver.8.0.7601.17514 (x64)


    Browser 3 : Google Chrome ver.29.0.1547.76 (x86)


    Browser 4 : Apple Safari ver.5.1.7.0 (x86)





    Code:

    Browsers.Item(btIExplorer).Navigate("http://news.bbc.co.uk") FAILS

    Browsers.Item(1)Navigate("http://news.bbc.co.uk") FAILS

    Browsers.Item(2).Navigate("http://news.bbc.co.uk") WORKS



    1 = IE 32 bit

    2 = IE 64 bit



    "btIExplorer" launches 32 bit IE.



    So it seems that:



    a) When you have both architectures of IE installed, TC only works with 64 bit

    b) TC only has predefined constants for browsers by name, ignoring architecture

    c) When you have both architectures of IE installed, "btIExplorer" points to the 32 bit

    d) However TC handles browser.run seems to work with 64 bit and not 32 bit when you have both. 



    I'm trying to get my hands on a 32bit machine here, and then will try to get a new trial version of TC to see how it behaves there - I'm guessing it should work - as surely by now plenty of users would have made lots of noise otherwise!



    If anyone can add to this, please do!