parallel-protractor

Running parallel end 2 end tests from the same spec file using Protractor

WARNING still work in progress, some dependency loading issues.

Install and use

npm i -D parallel-protractor

Then, instead the command protractor conf.js run the command to load parallel-protractor first

{
  "scripts": {
    "test": "protractor conf.js",
    "test-in-parallel": "node -r parallel-protractor node_modules/.bin/protractor conf.js"
  }
}

Why?

If you have a large file with long running end to end tests, you can refactor the long file into the smaller separate physical files. The you can configure parallel tests. Or you can just create "virtual" spec files on the fly using parallel-protractor! It overrides the Node require function called from Protractor and tells it that there is a file for each describe block.

License

Author: Kensho © 2016

• @kensho
• kensho.com

Support: if you find any problems with this library, open issue on Github

The MIT License (MIT)

Copyright (c) 2016 Kensho

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.