test: use various services to verify compatibility

Currently we are only testing using the selenium-standalone service.

Since other services interact with the browser differently we must run
the tests using those services to check we are compatible with them.

Update the test setup so that we check: Puppeteer (default wdio
behaviour), Chromedriver, Geckodriver and Selenium Standalone.

Author: olivierwilkinson

.eslintrc

@@ -10,7 +10,7 @@
     "project": "*/**/tsconfig.json"
   },
   "plugins": ["@typescript-eslint"],
-  "ignorePatterns": "wdio.conf.js",
+  "ignorePatterns": "wdio.conf.*",
   "rules": {
     "babel/new-cap": "off",
     "func-names": "off",

package.json

@@ -13,7 +13,11 @@
     "lint": "kcd-scripts lint",
     "test:unit": "kcd-scripts test --no-watch --config=jest.config.js",
     "validate": "kcd-scripts validate build,lint,test,typecheck",
-    "test": "wdio wdio.conf.js",
+    "test:puppeteer": "wdio wdio.conf.js",
+    "test:selenium-standalone": "wdio wdio.conf.selenium-standalone.js",
+    "test:chromedriver": "wdio wdio.conf.chromedriver.js",
+    "test:geckodriver": "wdio wdio.conf.geckodriver.js",
+    "test": "npm-run-all test:puppeteer test:selenium-standalone test:chromedriver test:geckodriver",
     "semantic-release": "semantic-release",
     "typecheck:async": "tsc -p ./test/async/tsconfig.json",
     "typecheck:sync": "tsc -p ./test/sync/tsconfig.json",
@@ -49,7 +53,11 @@
     "npm-run-all": "^4.1.5",
     "semantic-release": "^17.0.2",
     "ts-node": "^9.1.1",
-    "typescript": "^4.4.2"
+    "typescript": "^4.4.2",
+    "chromedriver": "^105.0.1",
+    "geckodriver": "^3.0.2",
+    "wdio-chromedriver-service": "^7.3.2",
+    "wdio-geckodriver-service": "^2.0.0"
   },
   "repository": {
     "type": "git",

wdio.conf.chromedriver.js

@@ -0,0 +1,6 @@
+const baseConfig = require('./wdio.conf')
+
+exports.config = {
+  ...baseConfig.config,
+  services: ['chromedriver'],
+}

wdio.conf.geckodriver.js

@@ -0,0 +1,16 @@
+const baseConfig = require('./wdio.conf')
+
+exports.config = {
+  ...baseConfig.config,
+  services: ['geckodriver'],
+  capabilities: [
+    {
+      maxInstances: 5,
+      browserName: 'firefox',
+      acceptInsecureCerts: true,
+      'moz:firefoxOptions': {
+        args: process.env.CI ? ['--headless'] : [],
+      },
+    },
+  ]
+}

wdio.conf.js

@@ -61,14 +61,6 @@ exports.config = {
         args: process.env.CI ? ['--headless'] : [],
       },
     },
-    {
-      maxInstances: 5,
-      browserName: 'firefox',
-      acceptInsecureCerts: true,
-      'moz:firefoxOptions': {
-        args: process.env.CI ? ['--headless'] : [],
-      },
-    },
   ],
   //
   // ===================
@@ -117,12 +109,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.
-  services: [
-    [
-      'selenium-standalone',
-      {drivers: {firefox: true, chrome: !process.env.CI || {version: '94'}}},
-    ],
-  ],
+  services: [],
 
   // Framework you want to run your specs with.
   // The following are supported: Mocha, Jasmine, and Cucumber

wdio.conf.selenium-standalone.js

@@ -0,0 +1,19 @@
+const baseConfig = require('./wdio.conf')
+
+exports.config = {
+  ...baseConfig.config,
+  capabilities: [
+    ...baseConfig.config.capabilities,
+    {
+      maxInstances: 5,
+      browserName: 'firefox',
+      acceptInsecureCerts: true,
+      'moz:firefoxOptions': {
+        args: process.env.CI ? ['--headless'] : [],
+      },
+    },
+  ],
+  services: [
+    ['selenium-standalone', {drivers: {firefox: true, chrome: true}}]
+  ],
+}