Skip to content
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
This repository was archived by the owner on Jul 29, 2024. It is now read-only.

Protractor hangs when pointing to non existing spec file in multi capabilities #4665

@wouterpol

Description

@wouterpol

I am running protractor with multi capabilities and specific spec files. When one of the spec files does not exists, that multi capability completely hangs and never exits. The other multi capability process continues and when it is finished, protractor keeps waiting on the hanging multi capability I/launcher - 1 instance(s) of WebDriver still running.
The only way to recover, is to find the correct Node.js process and kill it. The hanging multi capability will exit with the following message: Unhandled rejection Error: ENOENT: no such file or directory, stat '<location of non existing spec file>' and will continue with other defined spec files.

I'm using cucumber on top of Protractor. Hence the .feature files as specs.

  • Node Version: 6.11.2
  • Protractor Version: 5.2.2
  • Angular Version: N/A
  • Browser(s): N/A
  • Operating System and Version Windows 10
  • Your protractor configuration file
  multiCapabilities: [{
    browserName: 'chrome',
    specs: ['NonExistingSpec.feature'],
    chromeOptions: {
      args: ['--disable-web-security --user-data-dir'],
    }
  }, {
    browserName: 'chrome',
    specs: ['ExistingSpec.feature'],
    chromeOptions: {
      args: ['--disable-web-security --user-data-dir']
    }
  }],
  • A relevant example test

    • Configure the multi capabilities: one to a existing spec file, the other one to a non existing spec file.
    • Run the test
  • Output from running the test

- Test 1 finishes successful - 
[chrome #11] [13:50:25] I/local - Shutting down selenium standalone server.

[13:50:25] I/testLogger -

[13:50:25] I/launcher - 1 instance(s) of WebDriver still running
[13:50:31] I/testLogger -
-- COMPLETELY HANGS AFTER THIS POINT -- 
  • Steps to reproduce the bug
    Configure the multi capabilities: one to a existing spec file, the other one to a non existing spec file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions