本地Docker流水线运行Nightwatch+Selenium报错求助

Hey there, sorry you're stuck with this Nightwatch + Docker + Selenium issue! Let's walk through common troubleshooting steps to get your tests running smoothly.

1. Check Docker Network Accessibility #

The biggest pain point here is usually network connectivity between your Nightwatch container, Selenium, and the target app you're testing:

• If you're testing a local web app running on your host machine, replace localhost in your test file or Nightwatch config with host.docker.internal (this works for Docker Desktop on Windows/macOS; for Linux, add --add-host=host.docker.internal:host-gateway to your docker run command).
• If Selenium is running in a separate Docker container, make sure both Nightwatch and Selenium are on the same Docker network. Create a dedicated network with docker network create nightwatch-network, then run both containers with --network nightwatch-network—you can then reference Selenium by its container name in your Nightwatch config (e.g., "selenium_host": "selenium-chrome").
• Verify port mappings: If Selenium listens on port 4444, ensure that port is exposed in the Selenium container and accessible from your Nightwatch container.

2. Validate Your nightwatch.json Config #

Double-check these critical settings in your config file:

• Selenium Server Details: Ensure selenium_host and selenium_port point to the correct location of your Selenium instance. If Selenium runs inside the same container as Nightwatch, use localhost; if it's a separate container, use the container name.
• Browser Driver Configuration: For Chrome (the most common use case), add these args to avoid Docker-specific issues:

  "chrome": {
    "desiredCapabilities": {
      "browserName": "chrome",
      "chromeOptions": {
        "args": ["--no-sandbox", "--disable-dev-shm-usage", "--headless=new"]
      }
    }
  }
  

• Test Target URL: Make sure the URL in your test file is reachable from the Docker container (again, use host.docker.internal instead of localhost for host apps).

3. Inspect Your Test File (nw-example.test.js) #

• Isolate issues with a simple smoke test to rule out complex selector or action problems:

  module.exports = {
    'Smoke test: Load target page': function(browser) {
      browser
        .url('http://host.docker.internal:3000') // Replace with your app's actual URL
        .waitForElementVisible('body')
        .assert.titleContains('Your App Title')
        .end();
    }
  };
  

• Avoid hardcoding localhost anywhere in the test—use a config variable instead to easily adjust for Docker environments.

4. Dig Into Error Logs #

Since you mentioned encountering an error, use logs to pinpoint the root cause:

• Run your Docker container with verbose logging enabled (add -e DEBUG=nightwatch* to your docker run command) to see detailed Nightwatch output.
• Check Selenium logs if it's a separate container: Use docker logs <selenium-container-name> to spot browser startup failures or connection errors.
• Common errors to watch for:

  ECONNREFUSED: Nightwatch can't reach Selenium—double-check network/port settings.
  NoSuchElementError: Either your selector is incorrect, or the target page isn't loading properly (verify the URL is reachable).
  SessionNotCreatedException: Usually a browser driver mismatch—ensure your Selenium version matches the browser driver version in your Docker image.

5. Verify Your Docker Image Setup #

• If using a custom Docker image, confirm it includes all required dependencies:
  • Node.js (for running Nightwatch)
  • The target browser (Chrome/Firefox)
  • Matching browser drivers (chromedriver/geckodriver)
  • Selenium Server (if running it inside the same container)
• Alternatively, use the official Nightwatch Docker image nightwatchjs/nightwatch—it comes pre-configured with Selenium and browsers to avoid setup gaps.

If you can share the specific error message you're seeing, we can narrow this down even further!

内容的提问来源于stack exchange，提问作者Matthew Serna