Error on using CUITe_BrowserWindow.CurrentBrowser = "chrome";

Dec 20, 2013 at 6:19 PM
Hi,

I am having trouble with launching the target application in the Chrome browser.

After using CUITe_BrowserWindow.CurrentBrowser = "chrome"; and running the script the chrome browser up followed by the below error:

The chromedriver.exe file does not exist in the current directory or in a directory on the PATH environment variable. The driver can be downloaded at http://code.google.com/p/chromium/downloads/list.

Where is the expected location to load the "chromedriver.exe" file as I tried uploading it inside the actual project folder but that still gets me the above error.

Regards,
Ankit
Coordinator
Dec 20, 2013 at 6:48 PM
I'm thinking chromedriver.exe at least needs to be included in the output directory:
  1. Right-click on chromedriver.exe that is included in the project in "Solution Explorer" in Visual Studio and click properties.
  2. Set "Copy to Output Directory" to "Copy if newer" or "Copy always".
  3. Rebuild and rerun the test.
If it still fails, you may need to include it as a DeploymentItem:
  1. Add the DeploymentItem attribute to the test class as follows:
    [DeploymentItem("chromedriver.exe")]
  2. Enabled deployment in your test settings:
    a. Click on Test (menu item) > Edit Test Settings > Local (Local.testsettings)
    b. Click Deployment > Check "Enable deployment"
    c. Click Apply
  3. Rebuild and rerun the test.
Otherwise, you can just include it in the PATH environment variable:
  1. Click Start > Right-click Computer > Properties
  2. Click "Advanced system settings"
  3. Click the "Environment Variables..." button.
  4. Select the PATH user variable
  5. Click on the "Edit..." button
  6. Enter the directory where chromedriver.exe exists on your system
    Insert a semicolon between other paths that may already exist
  7. Click OK
  8. Click OK
  9. Rebuild and rerun the test
Marked as answer by saxenaankit123 on 12/20/2013 at 12:31 PM
Dec 20, 2013 at 7:32 PM
Edited Dec 20, 2013 at 7:33 PM
Thanks for the resolution the part where we include the ChromeDriver as a part of the DeploymentItem worked out for me.