webdriverio Ошибка: не удалось запросить заголовки из chromedriver_mac64.zip: Ошибка: прочитать ECONNRESET - Mac OSX

Question

Я пишу тесты в webdriverio для одного из приложений. Я запускаю сервер селена и запускаю следующую команду

./node_modules/.bin/wdio wdio.conf.js

Когда я запускаю это на своем старом компьютере с Windows, он работает нормально, теперь, когда у меня есть новый Mac, он не работает. Ниже приведена трассировка стека.

A service failed in the 'onPrepare' hook
Error: Could not request headers from https://chromedriver.storage.googleapis.com/2.43/chromedriver_mac64.zip: Error: read ECONNRESET
at Request.<anonymous> (/Users/fdfgd/Desktop/test_scripts/test/node_modules/selenium-standalone/lib/install.js:552:8)
at Object.onceWrapper (events.js:286:20)
at Request.emit (events.js:198:13)
at Request.EventEmitter.emit (domain.js:448:20)
at Request.onRequestError (/Users/v6x5932/Desktop/test_scripts/test/node_modules/request/request.js:881:8)
at ClientRequest.emit (events.js:198:13)
at ClientRequest.EventEmitter.emit (domain.js:448:20)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:198:13)
at TLSSocket.EventEmitter.emit (domain.js:448:20)

Continue...
Wrote xunit report "WDIO.xunit.chrome.0-0.xml" to [./test/reports].


0 passing (1.50s)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test@1.0.0 run-wdio-tests: `wdio wdio.conf.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the test@1.0.0 run-wdio-tests script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/dsfaf/.npm/_logs/2019-09-05T11_55_52_274Z-debug.log

Вот мой файл wdio.conf.js

exports.config = {

    //
    // ==================
    // Specify Test Files
    // ==================
    // Define which test specs should run. The pattern is relative to the directory
    // from which `wdio` was called. Notice that, if you are calling `wdio` from an
    // NPM script (see https://docs.npmjs.com/cli/run-script) then the current working
    // directory is where your package.json resides, so `wdio` will be called from there.
    //
    specs: [
        './test/specs/*.js'
    ],
    // Patterns to exclude.
    exclude: [
        // 'path/to/excluded/files'
    ],
    //
    // ============
    // Capabilities
    // ============
    // Define your capabilities here. WebdriverIO can run multiple capabilities at the same
    // time. Depending on the number of capabilities, WebdriverIO launches several test
    // sessions. Within your capabilities you can overwrite the spec and exclude options in
    // order to group specific specs to a specific capability.
    //
    // First, you can define how many instances should be started at the same time. Let's
    // say you have 3 different capabilities (Chrome, Firefox, and Safari) and you have
    // set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec
    // files and you set maxInstances to 10, all spec files will get tested at the same time
    // and 30 processes will get spawned. The property handles how many capabilities
    // from the same test should run tests.
    //
    maxInstances: 10,
    //
    // If you have trouble getting all important capabilities together, check out the
    // Sauce Labs platform configurator - a great tool to configure your capabilities:
    // https://docs.saucelabs.com/reference/platforms-configurator
    //
    capabilities: [{
        // maxInstances can get overwritten per capability. So if you have an in-house Selenium
        // grid with only 5 firefox instances available you can make sure that not more than
        // 5 instances get started at a time.
        maxInstances: 5,
        //
        browserName: 'chrome',
        proxy: {
            proxyType: "MANUAL",
            httpProxy: "domain:port",
            // sslProxy: "domain:port"
        }
    }],
    //
    // ===================
    // Test Configurations
    // ===================
    // Define all options that are relevant for the WebdriverIO instance here
    //
    // By default WebdriverIO commands are executed in a synchronous way using
    // the wdio-sync package. If you still want to run your tests in an async way
    // e.g. using promises you can set the sync option to false.
    sync: true,
    //
    // Level of logging verbosity: silent | verbose | command | data | result | error
    logLevel: 'silent',
    //
    // Enables colors for log output.
    coloredLogs: true,
    //
    // Warns when a deprecated command is used
    deprecationWarnings: true,
    //
    // If you only want to run your tests until a specific amount of tests have failed use
    // bail (default is 0 - don't bail, run all tests).
    bail: 0,
    //
    // Saves a screenshot to a given path if a command fails.
    screenshotPath: './errorShots/',
    //
    // Set a base URL in order to shorten url command calls. If your `url` parameter starts
    // with `/`, the base url gets prepended, not including the path portion of your baseUrl.
    // If your `url` parameter starts without a scheme or `/` (like `some/path`), the base url
    // gets prepended directly.
    baseUrl: 'http://localhost',
    //
    // Default timeout for all waitFor* commands.
    waitforTimeout: 10000,
    //
    // Default timeout in milliseconds for request
    // if Selenium Grid doesn't send response
    connectionRetryTimeout: 90000,
    //
    // Default request retries count
    connectionRetryCount: 3,
    //
    // Initialize the browser instance with a WebdriverIO plugin. The object should have the
    // plugin name as key and the desired plugin options as properties. Make sure you have
    // the plugin installed before running any tests. The following plugins are currently
    // available:
    // WebdriverCSS: https://github.com/webdriverio/webdrivercss
    // WebdriverRTC: https://github.com/webdriverio/webdriverrtc
    // Browserevent: https://github.com/webdriverio/browserevent
    // plugins: {
    //     webdrivercss: {
    //         screenshotRoot: 'my-shots',
    //         failedComparisonsRoot: 'diffs',
    //         misMatchTolerance: 0.05,
    //         screenWidth: [320,480,640,1024]
    //     },
    //     webdriverrtc: {},
    //     browserevent: {}
    // },
    //
    // Test runner services
    // Services take over a specific job you don't want to take care of. They enhance
    // your test setup with almost no effort. Unlike plugins, they don't add new
    // commands. Instead, they hook themselves up into the test process.
    services: ['selenium-standalone'],
    //
    // Framework you want to run your specs with.
    // The following are supported: Mocha, Jasmine, and Cucumber
    // see also: http://webdriver.io/guide/testrunner/frameworks.html
    //
    // Make sure you have the wdio adapter package for the specific framework installed
    // before running any tests.
    framework: 'mocha',
    //
    // Test reporter for stdout.
    // The only one supported by default is 'dot'
    // see also: http://webdriver.io/guide/reporters/dot.html
    reporters: ['junit','allure'],
    reporterOptions: {
        junit: {
            outputDir: './test/reports'
        },
        allure: {
            outputDir: 'allure-results'
        }
    },

    //
    // Options to be passed to Mocha.
    // See the full list at http://mochajs.org/
    mochaOpts: {
        ui: 'bdd',
        timeout: 60000
    },
    //
    // =====
    // Hooks
    // =====
    // WebdriverIO provides several hooks you can use to interfere with the test process in order to enhance
    // it and to build services around it. You can either apply a single function or an array of
    // methods to it. If one of them returns with a promise, WebdriverIO will wait until that promise got
    // resolved to continue.
    /**
    * Gets executed once before all workers get launched.
    * @param {Object} config wdio configuration object
    * @param {Array.<Object>} capabilities list of capabilities details
    */
    // onPrepare: function (config, capabilities) {
    // },
    /**
    * Gets executed just before initialising the webdriver session and test framework. It allows you
    * to manipulate configurations depending on the capability or spec.
    * @param {Object} config wdio configuration object
    * @param {Array.<Object>} capabilities list of capabilities details
    * @param {Array.<String>} specs List of spec file paths that are to be run
    */
    // beforeSession: function (config, capabilities, specs) {
    // },
    /**
    * Gets executed before test execution begins. At this point you can access to all global
    * variables like `browser`. It is the perfect place to define custom commands.
    * @param {Array.<Object>} capabilities list of capabilities details
    * @param {Array.<String>} specs List of spec file paths that are to be run
    */
    // before: function (capabilities, specs) {
    // },
    /**
    * Runs before a WebdriverIO command gets executed.
    * @param {String} commandName hook command name
    * @param {Array} args arguments that command would receive
    */
    // beforeCommand: function (commandName, args) {
    // },

    /**
    * Hook that gets executed before the suite starts
    * @param {Object} suite suite details
    */
    // beforeSuite: function (suite) {
    // },
    /**
    * Function to be executed before a test (in Mocha/Jasmine) or a step (in Cucumber) starts.
    * @param {Object} test test details
    */
    // beforeTest: function (test) {
    // },
    /**
    * Hook that gets executed _before_ a hook within the suite starts (e.g. runs before calling
    * beforeEach in Mocha)
    */
    // beforeHook: function () {
    // },
    /**
    * Hook that gets executed _after_ a hook within the suite ends (e.g. runs after calling
    * afterEach in Mocha)
    */
    // afterHook: function () {
    // },
    /**
    * Function to be executed after a test (in Mocha/Jasmine) or a step (in Cucumber) ends.
    * @param {Object} test test details
    */
    // afterTest: function (test) {
    // },
    /**
    * Hook that gets executed after the suite has ended
    * @param {Object} suite suite details
    */
    // afterSuite: function (suite) {
    // },

    /**
    * Runs after a WebdriverIO command gets executed
    * @param {String} commandName hook command name
    * @param {Array} args arguments that command would receive
    * @param {Number} result 0 - command success, 1 - command error
    * @param {Object} error error object if any
    */
    // afterCommand: function (commandName, args, result, error) {
    // },
    /**
    * Gets executed after all tests are done. You still have access to all global variables from
    * the test.
    * @param {Number} result 0 - test pass, 1 - test fail
    * @param {Array.<Object>} capabilities list of capabilities details
    * @param {Array.<String>} specs List of spec file paths that ran
    */
    // after: function (result, capabilities, specs) {
    // },
    /**
    * Gets executed right after terminating the webdriver session.
    * @param {Object} config wdio configuration object
    * @param {Array.<Object>} capabilities list of capabilities details
    * @param {Array.<String>} specs List of spec file paths that ran
    */
    // afterSession: function (config, capabilities, specs) {
    // },
    /**
    * Gets executed after all workers got shut down and the process is about to exit.
    * @param {Object} exitCode 0 - success, 1 - fail
    * @param {Object} config wdio configuration object
    * @param {Array.<Object>} capabilities list of capabilities details
    */
    // onComplete: function(exitCode, config, capabilities) {
    // }
}

Я пробовал следующие подходы в файле wdio.conf.js

Подход 1: инструкция в нижнем регистре

 proxy: {
        proxyType: "manual",
        httpProxy: "http://domain:port"
    }

Подход 2: руководство в верхнем регистре

 proxy: {
        proxyType: "MANUAL",
        httpProxy: "http://domain:port"
    }

Подход 3: прокси с http://

 proxy: {
        proxyType: "MANUAL",
        httpProxy: "http://domain:port"
    }

Подход 4: прокси без http://

 proxy: {
        proxyType: "MANUAL",
        httpProxy: "http://domain:port"
    }

Не могли бы вы сообщить мне, в чем может быть проблема, я также попытался добавить прокси в сеанс терминала, и он все тот же

Answer 1

Это сообщение об ошибке...

Could not request headers from https://chromedriver.storage.googleapis.com/2.43/chromedriver_mac64.zip: Error: read ECONNRESET

... означает, что ChromeDriver не смог инициировать / создать новый веб- браузер, то есть сеанс браузера Chrome.

Ваша основная проблема заключается в несовместимости между версиями используемых вами двоичных файлов:

• Вы используете chromedriver=2.43
• Примечания к выпуску chromedriver=2.43 четко упоминают следующее:

Поддерживает Chrome v69-71

• Предположительно вы используете последнюю версию chrome= 76.0
• Примечания к выпуску ChromeDriver v76.0 четко упоминают следующее:

Поддерживает Chrome версии 76

Таким образом, между ChromeDriver v2.43 и браузером Chrome v76.0 существует явное несоответствие.

---

Решение

Гарантировать, что:

• ChromeDriver обновлен до текущего уровня ChromeDriver v76.0.
• Chrome обновлен до текущего уровня Chrome версии 76.0. (согласно примечаниям к выпуску ChromeDriver v76.0)
• Очистите свой Workspace Project через IDE и Rebuild ваш проект только с необходимыми зависимостями.
• Если ваша базовая версия веб-клиента слишком старая, удалите и установите последнюю версию GA и выпущенную версию веб-клиента.
• Выполните перезагрузку системы.
• Выполните свой @Testкак пользователь без полномочий root.