Forum Discussion

dipali's avatar
dipali
Occasional Contributor
7 years ago

Chrome39 doesn't work with TCv10 despite of all extensions installed

I have installed chrome v39 which is currently supported by TestComplete v10 [after TC installation] . I can see the testcomplete extension enabled in chrome. Also Testcomplete install extensions dialog shows all the chrome extensions checked. But still TestComplete object spy isn't able to read objects and shows error message "Check if chrome extension is enabled or installed"

I have tried modifying the TC installation to re-install web components and chrome re-installation followed by machine restart but no luck!

Is there anything that I'm missing? I already have working test scripts for IE browser which I'm trying to configure on Chrome browser.
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    What specific version of TC 10 are you running?  Acording to https://support.smartbear.com/downloads/testcomplete/chrome-patches/, the version of TC 10 that supports Chrome 39 "out of the box" is 10.50.  If you are running 10.40 or earlier, it will not work.

     

    As a curiousity question.....  why are you testing using such an old version of Chrome?  Chrome being what it is with auto-updates enabled by default, I really don't see how any user out there in the real world would ever be using such an old version of Chrome.

    • dipali's avatar
      dipali
      Occasional Contributor
      7 years ago
      I'm using TC v10.50.

      Well I did install latest chrome and it didnt work as the TC extension was
      disabled in chrome [common problem many people reported] and which I couldn't enable after all googling attempts. So I thought of installing v39 and the TC extension was at least enabled.

      Will TC v10 work with latest Chrome?
      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        7 years ago

        No... TC 10.5 will not work with Chrome 68.  And that's probably why the extension was disabled because it is not supported for the latest Chrome.

         

        As for the disabled extension in 68, there are several threads that have working solutions up here (there's a URL to go to) but it requires TC 12.50.