Protractor v0.14.0 Release Notes

  • 🚀 Note: Major version 0 releases are for initial development, and backwards incompatible changes may be introduced at any time.

    🔋 Features

    • (c579a1a), (f54fd5d) feat(webdriver-manager): redo the script to run and install selenium/webdriver

    Breaking Change. As outlined in Issue #296, redoing the way the selenium/webdriver install and run helper scripts work. Now, the 'webdriver-manager' script will be available either locally or globally (depending on how protractor was installed). It replaced install_selenium_standalone and the 'start' script that was provided after install. Run webdriver-manager update to download new versions of selected webdriver binaries. Run webdriver-manager start to start the standalone server. In addition, this fixes issues with running the server starter in Windows, and allows automated downloading of the IEDriver.

    Thanks to kurthong and vipper for their PRs with windows fixes, which were very useful in preparing this.

    • 0️⃣ (a69ebc3) feat(runner): use selenium and chromedriver from the default location if nothing else is specified

    🐛 Bug Fixes

    • 🔀 (1fa090c) fix(runner): merge should override entire arrays, not just parts of them

    Closes #304

    • 🌐 (a2afb4d) fix(element): element.all.get and element.all.first/last should wrap web elements

    Closes #307

    • (f3be172) fix(runner): running with chromeOnly should try to find chromedriver with .exe extension

    Closes #283

    💥 Breaking Changes

    • (c579a1a) feat(webdriver-manager): redo the script to run and install selenium/webdriver

    Breaking Change. Your old selenium/start script will continue to work, but install_selenium_standalone no longer exists. To do a clean update, remove the selenium folder. Then run webdriver-manager update

    • (a1c91a2) fix(config): Make all file paths in config files relative to the config file itself

    Breaking Change Previously, onPrepare and specs were relative to the location of the config, but seleniumServerJar and chromeDriver were relative to the cwd when the test was called. If you were calling the tests from somewhere other than the same directory as the config location, you will need to change the paths of seleniumServerJar and/or chromeDriver. Closes #222.