Skip to content

Running @vue/cli-plugin-e2e-nightwatch tests in parallel #7299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pdrivom opened this issue Sep 19, 2022 · 0 comments
Open

Running @vue/cli-plugin-e2e-nightwatch tests in parallel #7299

pdrivom opened this issue Sep 19, 2022 · 0 comments

Comments

@pdrivom
Copy link

pdrivom commented Sep 19, 2022

Version

5.0.8

Environment info

  System:
    OS: Linux 5.10 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 14.20.0 - /usr/bin/node
    Yarn: Not Found
    npm: 8.19.2 - /usr/bin/npm
  Browsers:
    Chrome: 105.0.5195.102
    Firefox: Not Found
  npmPackages:
    @intlify/vue-devtools:  9.2.2 
    @intlify/vue-i18n-loader: ^4.2.0 => 4.2.0 
    @oreliain/vue-i18n-extract-keys: ^2.1.1 => 2.1.1 
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1 
    @vue/babel-helper-vue-transform-on:  1.0.2 
    @vue/babel-plugin-jsx:  1.1.1 
    @vue/babel-plugin-transform-vue-jsx:  1.2.1 
    @vue/babel-preset-app:  5.0.8 
    @vue/babel-preset-jsx:  1.3.0 
    @vue/babel-sugar-composition-api-inject-h:  1.3.0 
    @vue/babel-sugar-composition-api-render-instance:  1.3.0 
    @vue/babel-sugar-functional-vue:  1.2.2 
    @vue/babel-sugar-inject-h:  1.2.2 
    @vue/babel-sugar-v-model:  1.3.0 
    @vue/babel-sugar-v-on:  1.3.0 
    @vue/cli-overlay:  5.0.8 
    @vue/cli-plugin-babel: ^5.0.8 => 5.0.8 
    @vue/cli-plugin-e2e-nightwatch: ^5.0.8 => 5.0.8 
    @vue/cli-plugin-eslint: ^5.0.8 => 5.0.8 
    @vue/cli-plugin-router:  5.0.8 
    @vue/cli-plugin-vuex:  5.0.8 
    @vue/cli-service: ^5.0.8 => 5.0.8 
    @vue/cli-shared-utils:  5.0.8 
    @vue/compiler-core:  3.2.39 
    @vue/compiler-dom:  3.2.39 
    @vue/compiler-sfc: ^3.2.39 => 3.2.39 
    @vue/compiler-ssr:  3.2.39 
    @vue/component-compiler-utils:  3.3.0 
    @vue/devtools-api:  6.2.0 (6.2.1)
    @vue/reactivity:  3.2.39 
    @vue/reactivity-transform:  3.2.39 
    @vue/runtime-core:  3.2.39 
    @vue/runtime-dom:  3.2.39 
    @vue/server-renderer:  3.2.39 
    @vue/shared:  3.2.39 
    @vue/web-component-wrapper:  1.3.0 
    eslint-plugin-vue: ^8.7.1 => 8.7.1 
    vue: ^3.2.39 => 3.2.39 
    vue-eslint-parser:  8.3.0 
    vue-hot-reload-api:  2.3.4 
    vue-i18n: ^9.2.2 => 9.2.2 
    vue-input-autowidth: ^1.0.11 => 1.0.11 
    vue-loader:  17.0.0 (15.10.0)
    vue-router: ^4.1.5 => 4.1.5 
    vue-style-loader:  4.1.3 
    vue-template-es2015-compiler:  1.9.1 
    vuedraggable: ^4.1.0 => 4.1.0 
    vuex: ^4.0.2 => 4.0.2 

Steps to reproduce

Enabling test_workers on nightwatch.conf.js file and running script:

npm test:e2e

package.json
"test:e2e": "vue-cli-service test:e2e"

nightwatch.conf.js

...
default: {
  test_workers: true,
  desiredCapabilities: {
      browserName: 'chrome',
      'goog:chromeOptions': {
          args: ["--headless" ],
          w3c: false
      }
  }
  },
...

What is expected?

Several running tests workers should run without any connection issues to ChromeDriver (with same major version as Chrome).

INFO  Running end-to-end tests ...
Launching up to 8 concurrent test worker processes...
Starting ChromeDriver on auto-generated port...                                
ℹ Connected to ChromeDriver on port undefined (1168ms).  
...

What is actually happening?

All of the workers are unable to connect to ChromeDriver.

INFO  Running end-to-end tests ...
Launching up to 8 concurrent test worker processes...
...
⚠ Failed to connect to ChromeDriver on localhost with port 9515.

This started to happen after updating @vue/cli-plugin-e2e-nightwatch from v4 to v5.0.8 (Nightwatch updated from v1 to v2).
This package has Nightwatch as dependency with version 2.0.5 (current -> 2.3.7).
In the Nightwatch version 2.2.3 was fixed the following issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant