add ci wdio config + update workflow

Author: IdosApplitools

.github/workflows/test.yml

@@ -29,4 +29,4 @@ jobs:
         run: npm install chromedriver --detect_chromedriver_version
 
       - name: Execute all tests
-        run: npm test
+        run: npm run test:ci

package.json

@@ -4,7 +4,8 @@
   "description": "An example project for WebdriverIO 7 JavaScript using Applitools Ultrafast Grid",
   "main": "index.js",
   "scripts": {
-    "test": "wdio"
+    "test": "wdio",
+    "test:ci": "wdio wdio-ci.conf.js"
   },
   "author": "Applitools Team <team@applitools.com> (http://www.applitools.com/)",
   "license": "ISC",

wdio-ci.conf.js

@@ -0,0 +1,23 @@
+// For Demonstration
+// ---
+// In order to run WebdriverIO and subsequently an instance of Chrome using
+// continuous integration, particularly in this case, a GitHub Actions workflow,
+// we need to run Google Chrome headless. Here we're pulling in the base config
+// defined at wdio.conf.js and applying a new capabilities configuration that
+// adds the headless configuration to Chrome. When running Chrome headless
+// locally on a desktop environment, you will not be able to visibly see the
+// tests running in the browser.
+
+const baseConfig = require('./wdio.conf.js');
+
+exports.config = Object.assign({}, baseConfig.config, {
+  capabilities: [
+    {
+      maxInstances: 5,
+      browserName: 'chrome',
+      'goog:chromeOptions': {
+        args: ['--headless', '--disable-gpu'],
+      },
+    },
+  ],
+})

wdio.conf.js

@@ -61,7 +61,7 @@ exports.config = {
         browserName: 'chrome',
         acceptInsecureCerts: true,
         'goog:chromeOptions': {
-            args: ['headless']
+            args: ['--headless', '--disable-gpu']
         }
         // If outputDir is provided WebdriverIO can capture driver session logs
         // it is possible to configure which logTypes to include/exclude.