运行WebdriverIO测试脚本时遇未知错误，请求技术支持

Hey there, let's figure out why your WebdriverIO script is throwing that truncated { Er... error. First off, that partial error message isn't enough to pinpoint the issue, so let's start by getting the full details, then walk through the most common causes.

Step 1: Get the Full Error Details #

The first thing you need is the complete error object, including stack traces and specific messages. Modify your script's catch block to print the full error using Node's util.inspect tool:

var webdriverio = require('webdriverio');
var util = require('util'); // Add this line
var options = { desiredCapabilities: { browserName: 'chrome' } };

webdriverio
.remote(options)
.init()
.url('http://www.google.com')
.getTitle().then(function(title) { console.log('Title was: ' + title); })
.end()
.catch(function(err) { 
  console.error('Full Error Details:');
  console.error(util.inspect(err, { depth: null, colors: true })); // Print full error
});

Run node test.js again—this will show you exactly what's going wrong, which makes troubleshooting way easier.

Common Causes & Fixes #

Once you have the full error, it's likely one of these issues:

1. ChromeDriver Isn't Installed or Accessible #

WebdriverIO needs ChromeDriver to communicate with Chrome. If it's missing or not in your system's PATH, you'll get a connection error.

• Fix:
  • Install the webdriver-manager tool to manage drivers automatically:

    npm install -g webdriver-manager
    webdriver-manager update
    webdriver-manager start
    

  • Keep the webdriver-manager start terminal window open, then run your test script in another window. Alternatively, specify the ChromeDriver path directly in your options:

    var options = { 
      desiredCapabilities: { browserName: 'chrome' },
      path: './chromedriver' // Adjust path to where your chromedriver is stored (use .exe extension on Windows)
    };
    

2. Chrome & ChromeDriver Version Mismatch #

ChromeDriver has strict version compatibility with Chrome. If your Chrome browser version doesn't match your ChromeDriver version, the driver can't launch the browser.

• Fix:
  • Check your Chrome version (Go to Chrome Settings → About Chrome).
  • Download the matching ChromeDriver version from the official ChromeDriver repository, or run webdriver-manager update to auto-download the correct version.

3. Outdated WebdriverIO Version #

Your script uses the older WebdriverIO v4 syntax, which might not play nice with newer Chrome/ChromeDriver versions.

• Fix:
  • If you want to stick with v4, ensure you have the correct dependencies:

    npm install webdriverio@4 --save-dev
    

  • Or upgrade to the latest WebdriverIO v8, which uses async/await for cleaner code and better compatibility:

    const { remote } = require('webdriverio');
    
    (async () => {
      const browser = await remote({
        capabilities: { browserName: 'chrome' }
      });
    
      await browser.url('http://www.google.com');
      const title = await browser.getTitle();
      console.log('Title was: ' + title);
    
      await browser.deleteSession();
    })().catch((err) => {
      console.error(err);
      process.exit(1);
    });
    

4. Stuck Chrome Processes or Permissions #

Sometimes leftover Chrome processes can block the driver from launching a new instance, or you might lack permissions to start Chrome.

• Fix:
  • Close all Chrome windows and kill any remaining Chrome/chromedriver processes via your task manager (Windows) or activity monitor (Mac/Linux).
  • On Linux, if you're running into permission issues, try running the script with sudo (though this should be a last resort).

Once you work through these steps, your script should run smoothly. Let the full error message guide you to the exact fix!

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