From 4f6023e44c0083ed9f200987eaf998ba099299a2 Mon Sep 17 00:00:00 2001 From: Kazuhito Yokoi Date: Tue, 5 Nov 2019 11:40:20 +0900 Subject: [PATCH] Support UI testing on the latest Google Chrome --- scripts/install-ui-test-dependencies.sh | 3 ++- test/editor/wdio.conf.js | 4 ++-- 2 files changed, 4 insertions(+), 3 deletions(-) mode change 100755 => 100644 scripts/install-ui-test-dependencies.sh diff --git a/scripts/install-ui-test-dependencies.sh b/scripts/install-ui-test-dependencies.sh old mode 100755 new mode 100644 index 0148633be..608c32f70 --- a/scripts/install-ui-test-dependencies.sh +++ b/scripts/install-ui-test-dependencies.sh @@ -4,4 +4,5 @@ npm install --no-save \ wdio-mocha-framework@^0.6.4 \ wdio-spec-reporter@^0.1.5 \ webdriverio@^4.14.1 \ - chromedriver@2 + chromedriver@^78.0.1 \ + @wdio/cli@^5.15.6 diff --git a/test/editor/wdio.conf.js b/test/editor/wdio.conf.js index 7822cbbf3..37426cf14 100644 --- a/test/editor/wdio.conf.js +++ b/test/editor/wdio.conf.js @@ -61,7 +61,7 @@ exports.config = { maxInstances: 2, // browserName: 'chrome', - chromeOptions: { + 'goog:chromeOptions': { args: process.env.NODE_RED_NON_HEADLESS // Runs tests with opening a browser. ? ['--disable-gpu'] @@ -134,7 +134,7 @@ exports.config = { // 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. - port: '9515', + port: 9515, path: '/', services: ['chromedriver'], //