Giter Club home page Giter Club logo

blueimp / wdio Goto Github PK

View Code? Open in Web Editor NEW
295.0 10.0 52.0 1.1 MB

Docker setup for WebdriverIO with automatic screenshots, image diffing and screen recording support for containerized versions of Chrome and Firefox on Linux, mobile versions of Chrome and Firefox on Android as well as Safari on iOS, Safari on macOS and Edge on Windows.

Home Page: https://hub.docker.com/r/blueimp/wdio

License: MIT License

Dockerfile 2.80% JavaScript 35.93% HTML 5.33% Python 17.56% Shell 17.37% PowerShell 14.48% CSS 6.53%

wdio's Introduction

WDIO

Docker setup for WebdriverIO with automatic screenshots, image diffing and screen recording support for containerized versions of Chrome and Firefox on Linux, mobile versions of Chrome and Firefox on Android as well as Safari on iOS, Safari on macOS and Edge on Windows.

Contents

Usage

Run the tests:

docker-compose run --rm wdio [wdio.conf.js]

Stop and remove the container set:

docker-compose down

Tags

For any critical infrastructure (e.g. your company's Continuous Integration tests) it is strongly recommended to use your own tagged Docker images instead of blueimp/wdio and the other provided sample Docker images directly, as changes in the included software might break your tests inadvertently. See also:

Playwright

An alternative example end-to-end testing setup using the Playwright framework can be found at blueimp/playwright-example.

License

Released under the MIT license.

Author

Sebastian Tschan

wdio's People

Contributors

blueimp avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wdio's Issues

What is the correct method to add and use a node module not included in repo?

Greetings, this is more of a question than an issue (sorry if this is the incorrect location to ask). Let's say I wanted to add a node package manager module, such as request-promise, to be available when running tests in Firefox. How would I got about doing that?

I have tried adding the module to the list of modules to be installed globally, and require it in the test file (const rp = require('request-promise');), but then when I run tests in Firefox, I get the error: Cannot find module 'request-promise'.

Thanks in advance.
Screen Shot 2019-03-28 at 4 20 47 PM

How to pull old version of the image?

After the latest release, getting the following error on installing packages

While resolving:
npm ERR! Found: [email protected]
npm ERR! node_modules/webdriverio
npm ERR! webdriverio@"^6.1.9" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webdriverio@"^4.0.7" from [email protected]
npm ERR! node_modules/wdio-screenshot
npm ERR! dev wdio-screenshot@"^0.6.0" from the root project

the old version of the image is not present in dockerhub. how can i pull the old version of this image? Thank you

Problem with WDIO v4

I want to use your blueimp/wdio solution to execute WDIO tests in an own project, because I like this solution and it is really easy to use, also in combination with Jenkins. So, I’ve tried to make it useful for my project, but I have an issue with it and hope you can help me or can give me some recommendations :)))

So, what did I do:

  • I copied the Dockerfile, docker-compose.yml and chrome.js to my own project
  • I updated all these files and built an own docker image
  • Dockerfile extended with some more tools and my own package.json as base for the npm install
  • updated docker-compose.yml that uses my own docker image
    updated chrome.js

Now the problem is that it is not running with my own docker image based on the updated Dockerfile. The difference between your project https://github.com/blueimp/wdio and my project is the WDIO version. You are using WDIO v5 and we are still using WDIO v4. Maybe that could be the reason.

When I try to start a simple test (via docker-compose run --rm wdio chrome.js --spec=test/google.js), that only opens the google page, then it’s really fine while using your docker image (with WDIO v5) in docker-compose.yml. But when I’m using my docker image (with WDIO v4) then I get this error:

grme:web-client-uat GRme$ docker-compose run --rm wdio chrome.js --spec=test/google.js
Starting web-client-uat_chromedriver_1 ... done
Starting web-client-uat_geckodriver_1  ... done
Waiting for host: chromedriver:4444 ... ok
Waiting for host: geckodriver:4444  ... ok
ERROR: connect ECONNREFUSED 127.0.0.1:4444
chrome
    at new RuntimeError (/usr/lib/wdio/node_modules/webdriverio/build/lib/utils/ErrorHandler.js:143:12)
    at Request._callback (/usr/lib/wdio/node_modules/webdriverio/build/lib/utils/RequestHandler.js:342:43)
    at self.callback (/usr/lib/wdio/node_modules/request/request.js:185:22)
    at Request.emit (events.js:198:13)
    at Request.EventEmitter.emit (domain.js:448:20)
    at Request.onRequestError (/usr/lib/wdio/node_modules/request/request.js:881:8)
    at ClientRequest.emit (events.js:203:15)
    at ClientRequest.EventEmitter.emit (domain.js:448:20)
    at Socket.socketErrorListener (_http_client.js:392:9)
    at Socket.emit (events.js:198:13)

The big problem is that we are not able to switch to WDIO v5 in a fast way because therefore we have to do a refactoring that will take a lot of time and I’m the only testautomation guy at the moment ;) So, I try to make it runnable also with WDIO v4.

This is my Dockerfile:

FROM alpine:3.10
RUN echo '@edgetesting http://dl-cdn.alpinelinux.org/alpine/edge/testing' \
  >> /etc/apk/repositories
RUN apk --no-cache add \
    nodejs \
    npm \
    ffmpeg \
    android-tools@edgetesting \
    nano \
  	git \
  	curl \
  	wget \
  	bzip2 \
  	xvfb \
  	vim \
  	xterm \
  && npm install -g \
    npm@latest \
  && rm -rf \
    /tmp/* \
    /root/.npm
WORKDIR /usr/lib/wdio
COPY package.json ./
RUN npm install \
  && npm audit fix \
  && rm -rf \
    /tmp/* \
    /root/.npm
ENV NODE_PATH=/usr/lib/wdio/node_modules
ENV PATH=$PATH:/usr/lib/wdio/node_modules/.bin
COPY bin/wait-for-hosts.sh /usr/local/bin/wait-for-hosts
RUN chmod 777 /usr/local/bin/wait-for-hosts
RUN chmod 777 -Rf ${NODE_PATH}
RUN adduser -D -u 1000 wdio
USER wdio
WORKDIR /opt
ENTRYPOINT ["wait-for-hosts", "--", "wdio"]

This is my package.json (with WDIO v4):

{
  "name": "webdriverio",
  "version": "1.3.0",
  "description": "Automated Testing (End2End, Rest API)",
  "main": "index.js",
  "dependencies": {
    "asserts": "4.0.2",
    "dotenv": "8.1.0",
    "fetch": "1.1.0",
    "html2json": "1.0.2",
    "json-query": "2.2.2",
    "json-to-html-form": "1.7.0",
    "mochawesome-report-generator": "3.1.5",
    "moment": "2.24.0",
    "promise": "8.0.3",
    "replace-in-file": "4.1.3",
    "request": "2.88.0",
    "request-promise": "4.2.4",
    "swagger-walk": "github:paulvollmer/swagger-walk",
    "wdio-screen-commands": "2.10.0",
    "webdriverio": "4.14.4"
  },
  "devDependencies": {
    "chai": "4.2.0",
    "chromedriver": "latest",
    "config": "3.2.2",
    "eslint": "6.4.0",
    "eslint-config-google": "0.14.0",
    "find": "0.3.0",
    "frisby": "2.1.2",
    "fs-extra": "8.1.0",
    "geckodriver": "latest",
    "hippie-swagger": "3.2.0",
    "jest": "24.9.0",
    "jest-html-reporter": "2.6.2",
    "jest-junit": "8.0.0",
    "jshint": "2.10.2",
    "mocha": "6.2.1",
    "mochawesome": "4.1.0",
    "scripty": "1.9.1",
    "selenium-server-standalone-jar": "3.141.59",
    "selenium-standalone": "6.16.0",
    "supertest": "4.0.2",
    "wdio-allure-reporter": "0.8.3",
    "wdio-chromedriver-service": "5.0.2",
    "wdio-firefox-profile-service": "0.1.3",
    "wdio-junit-reporter": "0.4.4",
    "wdio-mocha-framework": "0.6.4",
    "wdio-mochawesome-reporter": "2.0.1",
    "wdio-sauce-service": "0.4.14",
    "wdio-selenium-standalone-service": "0.0.12",
    "wdio-spec-reporter": "0.1.5",
    "winston": "3.2.1",
    "xunit-viewer": "5.1.11",
    "yargs": "14.0.0"
  },
  "prettier": {
    "arrowParens": "always",
    "bracketSpacing": true,
    "singleQuote": true,
    "trailingComma": "all",
    "printWidth": 100
  },
  "scripts": {
    "prepare-on-unix": "chmod -Rf 777 ./scripts/ && chmod -Rf 777 ./scripts-win/ && dos2unix ./scripts/* && unix2dos ./scripts-win/*",
    "clear-screenshots": "scripty",
    "test": "scripty",
    "npm-test": "scripty",
    "clear-test": "scripty",
    "clear-npm-test": "scripty",
    "postResults": "scripty",
    "test-postResults": "scripty",
    "clear-test-postResults": "scripty",
    "generateMochawesome": "scripty",
    "npm-install-and-run-all-rest-tests": "scripty",
    "npm-install-and-run-rest-tests": "scripty",
    "run-all-rest-tests": "scripty",
    "run-rest-tests": "scripty",
    "analyze-report-for-exit-code": "scripty"
  },
  "author": "Martin"
}

This is my chrome.js (WDIO config file):

'use strict';

exports.config = Object.assign({}, require('./hooks'), {
  hostname: 'chromedriver',
  path: '/',
  capabilities: [
    {
      // Set maxInstances to 1 if screen recordings are enabled:
      // maxInstances: 1,
      browserName: 'chrome',
      'goog:chromeOptions': {
        // Disable headless mode if screen recordings are enabled:
        args: ['--headless', '--window-size=1440,900']
      }
    }
  ],
  logLevel: 'error',
  reporters: ['spec'],
  framework: 'mocha',
  mochaOpts: {
    timeout: 60000
  },
  specs: ['test/**/*.js'],
  maximizeWindow: true,
  screenshots: {
    saveOnFail: true
  },
  videos: {
    enabled: false,
    resolution: '1440x900',
    startDelay: 500,
    stopDelay: 500
  },
  assetsDir: '/home/webdriver/assets/',
  mailhog: {
    host: 'mailhog'
  }
});

And finally this is my docker-compose.yml:

version: '3.7'
services:
  chromedriver:
    image: blueimp/chromedriver
    init: true
    tmpfs: /tmp
    environment:
      - DISABLE_X11=false
      - ENABLE_VNC=true
      - EXPOSE_X11=true
    volumes:
      - ./assets:/home/webdriver/assets:ro
    ports:
      - 127.0.0.1:5900:5900
  geckodriver:
    image: blueimp/geckodriver
    init: true
    tmpfs: /tmp
    shm_size: 2g
    environment:
      - DISABLE_X11=false
      - ENABLE_VNC=true
      - EXPOSE_X11=true
    volumes:
      - ./assets:/home/webdriver/assets:ro
    ports:
      - 127.0.0.1:5901:5900
  wdio:
    #image: blueimp/wdio:latest
    image: myimage:latest
    init: true
    #read_only: true
    tmpfs:
      - /tmp
      - /home/wdio/.android
    environment:
      - WAIT_FOR_HOSTS=
          chromedriver:4444
          geckodriver:4444
      - WINDOWS_HOST
      - ANDROID_SERIAL
      - PLATFORM_VERSION
      - DEVICE_NAME
      - ORIENTATION
      - MACOS_ASSETS_DIR=$PWD/assets/
      - WINDOWS_ASSETS_DIR
    volumes:
      - .:/opt
      #- ./reports:/opt/reports
    depends_on:
      - chromedriver
      - geckodriver

Maybe you have some recommendations or tips for me what I can do to make it runnable for me.

It would be very, very cool and you would make me really happy :))) I hope I will get an answer from you.

How to screencast a url?

Any examples with screenshots or screencasting? Also does screencasting support recording with an alpha channel? (like to webm or mov format)?

Moving from blueimp/nightwatch to blueimp/wdio

Since your previous package has been archived now we i want to move on to this one so are there any docs available for this so ? Building all things which come from nightwatch to this wdio would cost us a big amount of time

Question: Any plans on adding allure reporting? (or any other reporting mechanism)

I tried added @wdio/allure-reporter to the npm global install list in Dockerfile

RUN apk --no-cache add \
    nodejs \
    npm \
    ffmpeg \
    android-tools@edgetesting \
  && npm install -g \
    npm@latest \
    @wdio/cli@^5.7.13 \
    @wdio/local-runner@^5.7.13 \
    @wdio/mocha-framework@^5.7.13 \
    @wdio/spec-reporter@^5.7.13 \
    @wdio/allure-reporter \
    @wdio/sync@^5.7.13 \
    chai@^4.2.0 \
    mailhog@^4.1.0 \
    uuid@^3.3.2 \
    wdio-screen-commands@^2.6.0 \
    webdriverio@^5.7.13 \
    lodash@^4.17.11 \

and added the config in wdio.conf.js

reporters: ["spec", "allure"],
  reporterOptions: {
    allure: {
      outputDir: "allure-results",
      disableWebdriverStepsReporting: true,
      disableWebdriverScreenshotsReporting: true,
      useCucumberStepReporter: false
    }
  },

Here's the error I get

Stderr:
wdio_1          | [0-0] 2019-04-17T11:59:36.703Z ERROR @wdio/local-runner: Failed launching test session: Error: Couldn't find plugin "allure" reporter, neither as wdio scoped package "@wdio/allure-reporter" nor as community package "wdio-allure-reporter". Please make sure you have it installed!
wdio_1          |     at initialisePlugin (/usr/lib/node_modules/@wdio/local-runner/node_modules/@wdio/utils/build/initialisePlugin.js:62:9)
wdio_1          |     at BaseReporter.initReporter (/usr/lib/node_modules/@wdio/local-runner/node_modules/@wdio/runner/build/reporter.js:189:51)
wdio_1          |     at Array.map (<anonymous>)
wdio_1          |     at new BaseReporter (/usr/lib/node_modules/@wdio/local-runner/node_modules/@wdio/runner/build/reporter.js:34:39)
wdio_1          |     at Runner.run (/usr/lib/node_modules/@wdio/local-runner/node_modules/@wdio/runner/build/index.js:89:21)
wdio_1          |     at process.on.m (/usr/lib/node_modules/@wdio/local-runner/build/run.js:37:20)
wdio_1          |     at process.emit (events.js:187:15)
wdio_1          |     at emit (internal/child_process.js:812:12)
wdio_1          |     at process._tickCallback (internal/process/next_tick.js:63:19)

Thoughts on what I'm doing wrong?

ERROR @wdio/config:ConfigParser:

2019-04-30 18:48:20 ☆ nickademous in ~
± |master ↑1 ↓2 S:387 U:367 ?:452 ✗| → docker run -it -v $(pwd):/usr/workspace blueimp/wdio sh
Unable to find image 'blueimp/wdio:latest' locally
latest: Pulling from blueimp/wdio
bdf0201b3a05: Pull complete
436b67d6d032: Pull complete
6e7ac5f22b73: Pull complete
68e94cea041c: Pull complete
bfe897812e06: Pull complete
Digest: sha256:5cfcfe1a43ef277e56584b820b8618b0d1744006f3e76292ae53b3bde69f410d
Status: Downloaded newer image for blueimp/wdio:latest
2019-05-01T04:52:45.887Z ERROR @wdio/config:ConfigParser: Failed loading configuration file: /opt/sh: Cannot find module '/opt/sh'
/usr/lib/node_modules/@wdio/cli/node_modules/@wdio/config/build/lib/ConfigParser.js:86
throw e;
^

Error: Cannot find module '/opt/sh'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at ConfigParser.addConfigFile (/usr/lib/node_modules/@wdio/cli/node_modules/@wdio/config/build/lib/ConfigParser.js:51:48)
at new Launcher (/usr/lib/node_modules/@wdio/cli/build/launcher.js:33:23)
at launch (/usr/lib/node_modules/@wdio/cli/build/run.js:87:20)
at run (/usr/lib/node_modules/@wdio/cli/build/run.js:64:12)
at Object.run (/usr/lib/node_modules/@wdio/cli/build/index.js:45:20)
at Object. (/usr/lib/node_modules/@wdio/cli/bin/wdio.js:11:21)

Question about integrating wdio-image-comparison-service

Followed your advise on building my own image. #6 (comment)

I tried to integrate wdio-image-comparison-service in my image by following their integrating guide. https://webdriver.io/blog/2019/05/18/visual-regression-for-v5.html

Seems to be failing at

npm install -g wdio-image-comparison-service

Just wondering if you have any insight into what might be wrong and how to fix it.
It looks like a mkdir permission issue to create a dir in /usr/lib/node_modules/

Any ideas on how to fix this? (any help would be appreciated)

Step 5/11 : RUN npm install -g wdio-image-comparison-service
 ---> Running in 8e26e11af505

> [email protected] install /usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (node-v64 ABI, musl) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error EACCES: permission denied, mkdir '/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build'
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:484:19)
gyp ERR! stack     at PythonFinder.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:406:16)
gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:16)
gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:153:21)
gyp ERR! System Linux 4.9.125-linuxkit
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build/Release" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"
gyp ERR! cwd /usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas
gyp ERR! node -v v10.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build/Release --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/wdio-image-comparison-service/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Linux 4.9.125-linuxkit
node-pre-gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/wdio-image-comparison-service/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas
node-pre-gyp ERR! node -v v10.16.0
node-pre-gyp ERR! node-pre-gyp -v v0.11.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/usr/lib/node_modules/wdio-image-comparison-service/node_modules/canvas/build/Release --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install 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!     /root/.npm/_logs/2019-07-10T19_50_11_908Z-debug.log
The command '/bin/sh -c npm install -g wdio-image-comparison-service' returned a non-zero code: 1

Version in "./docker-compose.yml" is unsupported.

cloned repo, ran the chrome command docker-compose run --rm wdio chrome and got this message in terminal:

docker-compose run --rm wdio chrome 
/home/matthew/.local/lib/python2.7/site-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

is there an instruction I am missing here?

Docker version 18.06.1-ce
Node 8.10.0
npm 6.9.0
Ubuntu 18.04.1 LTS

Question: Mac (host machine) cannot connect to Windows vm

I've followed all the steps described here. https://github.com/blueimp/wdio#internet-explorer

Here's my .env file

SERVER_HOST=192.168.94.1
# SERVER_PORT=8080
# WINDOWS_HOST=10.0.2.15 # Got my host ip with *ipconfig* in command prompt
WINDOWS_HOST=10.0.2.2 # I've tried this as well. same output.
WINDOWS_ASSETS_DIR=C:\Users\IEUser\Documents\assets\


Running the test gives me the following output

Starting kumarwdio_chromedriver_1 ... done
Starting kumarwdio_geckodriver_1  ... done
Starting kumarwdio_mailhog_1      ... done
Starting kumarwdio_example_1      ... done
Waiting for host: chromedriver:4444 ... ok
Waiting for host: geckodriver:4444  ... ok
Waiting for host: example:8080      ... ok
1
Execution of 1 spec files started at 2019-10-28T22:31:10.410Z

2019-10-28T22:31:10.418Z INFO @wdio/cli:Launcher: Run onPrepare hook
2019-10-28T22:31:10.426Z INFO @wdio/local-runner: Start worker 0-0 with arg: ie
[0-0] RUNNING in internet explorer - /test/specs/test.spec.js
[0-0] 2019-10-28T22:31:10.739Z INFO @wdio/local-runner: Run worker command: run
[0-0] 2019-10-28T22:31:11.955Z DEBUG @wdio/local-runner:utils: init remote session
[0-0] 2019-10-28T22:31:12.060Z INFO webdriver: [POST] http://10.0.2.2:4445/session
[0-0] 2019-10-28T22:31:12.061Z INFO webdriver: DATA { capabilities:
   { alwaysMatch: { browserName: 'internet explorer' },
     firstMatch: [ {} ] },
  desiredCapabilities: { browserName: 'internet explorer' } }
[0-0] 2019-10-28T22:32:27.283Z WARN webdriver: Request failed due to connect ECONNREFUSED 10.0.2.2:4445
[0-0] 2019-10-28T22:32:27.283Z INFO webdriver: Retrying 1/3
2019-10-28T22:32:27.283Z INFO webdriver: [POST] http://10.0.2.2:4445/session
[0-0] 2019-10-28T22:32:27.283Z INFO webdriver: DATA { capabilities:
   { alwaysMatch: { browserName: 'internet explorer' },
     firstMatch: [ {} ] },
  desiredCapabilities: { browserName: 'internet explorer' } }

Maybe my SERVER_HOST is not correct, but it doesn't seem like that matters since it's getting stuck in the Mac -> Windows VM communication.

Is there anything I'm doing wrong?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.