同一Linux机器运行Selenium Chrome测试遇WebDriverException，求免-D参数方案

If you can't modify the Selenium Node startup command to include the -Dwebdriver.chrome.driver parameter due to your complex system architecture, here are several reliable workarounds to get your Chrome tests running smoothly on Linux:

• Set a System Environment Variable
  Selenium automatically recognizes the WEBDRIVER_CHROME_DRIVER environment variable, or you can add the chromedriver path to your system's PATH:

  • For temporary use in your current shell session:

    # Option 1: Add chromedriver to system PATH
    export PATH=$PATH:/absolute/path/to/your/chromedriver
    # Option 2: Set dedicated driver path variable
    export WEBDRIVER_CHROME_DRIVER=/absolute/path/to/your/chromedriver
    

  • For permanent setup, add either line to your user's ~/.bashrc, ~/.zshrc, or system-wide /etc/profile file, then run source ~/.bashrc (or equivalent) to apply changes immediately.

• Specify the Driver Path in Your Test Code
  If you control the test codebase, explicitly set the driver property before initializing the ChromeDriver. For example, in Java:

  // Define the chromedriver path directly in your test code
  System.setProperty("webdriver.chrome.driver", "/absolute/path/to/chromedriver");
  ChromeOptions chromeOptions = new ChromeOptions();
  WebDriver driver = new ChromeDriver(chromeOptions);
  

  For remote tests using RemoteWebDriver, ensure the Selenium Node has access to the chromedriver via one of the other methods above—client code won't handle the driver path directly in this scenario.

• Use a Selenium Node Configuration File
  Create a JSON configuration file for your Selenium Node to define the chromedriver path alongside other capabilities. Example node-config.json:

  {
    "capabilities": [
      {
        "browserName": "chrome",
        "maxInstances": 5,
        "webdriver.chrome.driver": "/absolute/path/to/chromedriver"
      }
    ],
    "maxSession": 5,
    "port": 5555
  }
  

  Start the Node with this config instead of command-line parameters:

  java -jar selenium-server-standalone.jar -role node -nodeConfig node-config.json
  

• Move Chromedriver to a Default PATH Directory
  Place the chromedriver executable in a directory that's already in your system's PATH (like /usr/local/bin or /usr/bin) and ensure it has execute permissions:

  sudo cp /path/to/your/chromedriver /usr/local/bin/
  sudo chmod +x /usr/local/bin/chromedriver
  

  Selenium will automatically locate the driver in these standard directories without any explicit configuration.

Pick the method that best fits your system constraints—all of these will resolve the WebDriverException by ensuring the Selenium Node can find the ChromeDriver executable.

内容的提问来源于stack exchange，提问作者Ravikiran Kulkarni