Forum Discussion

Luukdb's avatar
Luukdb
Contributor
2 years ago

TestComplete cannot find chrome webdriver

Hello,

 

I am trying to get TestComplete to run headless tests. I am following this guide https://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/headless.html#local and I am running into the issue that TestComplete cannot download/see the needed WebDriver.

 

This is the JavaScript used in the guide.

function Test_Chrome_Headless()
{
  var server = "localhost";
  var capabilities = {
    "browserName": "chrome",
    "screenResolution": "1920x1080"
  };

  var url = "myurl";
  Browsers.RemoteItem(server, capabilities).Run(url);
}

 

I downloaded the chrome driver manually and created the path as shown above. But even with the driver in the correct location he cannot seem to open it. When I try to open the driver myself, it works.

Does anyone have an idea what I am doing wrong?

 

Kind regards,

Luuk

Debugging
Script Tests
Test Run
web testing
  • pkudrys's avatar
    pkudrys
    Contributor
    2 days ago

    Hi all, I'm currently experiencing the very same problem. I have drivers both for Chrome and Edge located at appropriate place:    
    <ProgramData>\SmartBear\WebDrivers\chrome
    <ProgramData>\SmartBear\WebDrivers\edge 

    Sadly the TC still says "Failed to find WebDriver...". Any idea what could be wrong or how to solve this problem?  

    PS: I also tried to downgrade MSEdge and appropriate webdriver to supported version 128, but the result is the same.  

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    2 years ago

    Hi,

     

    Just a wild guess: does driver version match Chrome version?

    What version of Chrome are you using? What version of TestComplete you are using?

    If Chrome is 113 and TC is 15.51 this might be the problem with Chrome support in TC 15.51 that is widely discussed now in a lot of threads.

    Otherwise, I would recommend to create Support request via the https://support.smartbear.com/testcomplete/message/ form.

     

    • Luukdb's avatar
      Luukdb
      Contributor
      2 years ago

      I was indeed using 113 and TC 15.51 but I downgraded Chrome to 112, and downloaded the drivers for 112.

       

      So if I am correct, this should work, right?