Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~4.0.13
->7.0.0
Release Notes
angular/protractor
v7.0.0
Compare Source
v6.0.0
Compare Source
Selenium 4 removes the control flow and most of these changes are based on those changes. To see the full list of changes, please refer to selenium-webdriver's CHANGELOG
Breaking changes
waitForAngularEnabled
Features
(cf43651)
chore(debugprint): convert debugprint to TypeScript (#5074)
(4672265)
chore(browser): remove timing issues with restart and fork (#5085)
closes #5031
(b4dbcc2)
chore(elementexplorer): remove explorer bin file (#5094)
closes #5092
(3b8f263)
chore(ignoreSynchornization): clean up to use waitForAngularEnabled (#5071)
(ffa3519)
chore(debugger): remove debugger and explore methods (#5070)
(c9db3f3)
chore(promises): remove q promises and webdriver promises (#5052)
(e22065c)
chore(promises): clean up driver providers and browser control flow (#5034)
Driver providers and tests:
Use native promises over q promises in driver providers
Remove driverProviderUseExistingWebDriver since the generation of the selenium server is already
accomplished when providing a selenium address in driverProvider.ts. Also clean up docs and tests.
Enabled the driverProviderLocal tests
Clean up JSDocs for q.promise
Basic lib spec:
Remove auto unwrap test for a WebElement. Reference PR #3471
Browser:
Remove control flow from waitForAngularEnabled, waitForAngular, and angularAppRoot in the
Browser class.
Dependencies
(96ae17c)
deps(jasmine): upgrade jasmine 3.3 (#5102)
(d213aa9)
deps(selenium): upgrade to selenium 4 (#5095)
elements workaround for WebElement.equals
added a better unhandled rejection warning message in the launcher
control flow)bal function wrappers for mocha (these wrappers went away with
fix the attach to session driver provider
Typing exported from Protractor:
removed ActionSequence and EventEmitter (actions is currently missing)
removed promise.Promise
fulfilled, filter, whener, delayed, createFlow, controlFlow, all,
Typings exported from WebDriver:
removed attachToSession
removed WebDriver instance methods: touchActions, call
removed WebElement getSize and getLocation for getRect
removed redefined global vars for testing
In the typings, we are missing Options.setScriptTimeout method. This should not impact users
unless they are using the driver.manage() method.
Tests:
fix element equals test
add missing 'await' in colorList test that is causing unhandled promise rejections.
remove control flow related tests
disable the install test. Installing from "file:../../" is not working.
fix the attach to session driver provider test to exit with a 1 if errors are encountered
(509f1b2)
deps(latest): upgrade to the gulp and typescript (#5089)
supported by gulpp 4 and remove run sequence since this feature is
(2def202)
deps(webdriver-manager): use replacement (#5088)
publish a beta release of use webdriver-manager-replacement until we
webdriver-manager
closes #5087
Miscellaneous
Minor fixes to remove the control flow completely and to prevent random execution order in Jasmine 3.
(0a2809e)
chore(types): fix types to use not @types/selenium-webdriver (#5127)
(84cdc50)
chore(jasmine): prevent random execution order in jasmine 3 (#5126)
v5.4.4
Compare Source
v5.4.3
Compare Source
typescript 3.7 compatibility
Resolves #5348 which was causing incompatibility with TypeScript 3.7
v5.4.2
Compare Source
Features
(db1b638)
feat(saucelabs): add sauceRegion support for eu datacenters (#5083)
This change allows user to define the backend region from sauce via the
sauceRegion
property,e.g.
Will run the test against
https://ondemand.eu-central-1.saucelabs.com:443/wd/hub/.
Will run the test against https://ondemand.saucelabs.com:443/wd/hub/
Fixes
fix(deps): @types/node is now a dev dependency
v5.4.1
Compare Source
Features
(7b08083)
feat(driverProvider): Add useExistingWebDriver driver provider (#4756)
(249e657)
feat(example): add examples of usage protractor framework with angular-material components;
(#4891)
Fixes
(39485ca)
fix(typo): fixed typo in EC expectation alias (#4952)
(07fefeb)
fix(browser): browser.navigate() return type. (#4932)
Changing return type of browser.navigate() to be Navigation instead of any.
(0b1820c)
fix(package-lock.json): update package-lock.json to match package.json. (#4931)
Dependencies
deps(webdriver_js_extender): update webdriver_js_extender to 2.1 (#4934)
v5.4.0
Compare Source
Features
feat(driverProvider) Adding browserstackProxy param in BrowserStack driverProvider (#4852)
Fixes
(492230a)
fix(generate_doc.sh): Use ES6 lib to compile down to ES5 (#4884)
(ed955e5)
fix(travisCI): Update Node versions (#4847)
(3702a70)
fix(local): Ensure webdriver.gecko.driver path is passed to Selenium (#4502)
(1c6a1a8)
fix(circleci): Switch to using circleci v2 syntax and fix build errors (#4837)
Dependencies
deps(webdriver_js_extender): update webdriver_js_extender to 2.0 (#4882)
v5.3.2
Compare Source
Fixes
(4e0a57c)
fix(test): fix async tests
Increase the scripts timeout
(c6703a5)
fix(doc): Spelling updates to comments in plugin.ts(#4797)
Updated some of the spelling errors/ punctuation mistakes for clearer understanding.
(76324b8)
fix(cli): add more verbose warning if '_debugger' module cannot be found. (#4800)
(f8f490a)
updated CHANGELOG based on sauceSeleniumAddress and sauceSeleniumUseHttp (#4793)
(6290f27)
fix(generate-docs): fix generate-docs.sh. (#4765)
Ignore generated unstaged files before checking out to new branch; otherwise, the git checkout
will fail.
Dependencies
fix(deps): Update saucelabs for security issue. (#4805)
v5.3.1
Compare Source
Features
feat(logger): Add log level configuration (#1451) (#4068)
Fixes
(c63b99e)
fix(grep): change excluded tests to disabled instead of pending (#4673)
(9348ccf)
docs(page_objects): Remove unnecessary "await" and "async" (#4732)
(4898db0)
docs(plugins) add protractor-cucumber-steps plugin to plugins.md (#4721)
(a7411b6)
docs(page_objects): Add async / await example (#4675)
v5.3.0
Compare Source
Features
(9d87982)
feat(config): allow to use newer versions of CoffeeScript (#4567)
CoffeeScript lost the hyphen in the module name about 9 months ago, all the new versions are
going to be released as coffeescript not the coffee-script
(6ba30e0)
feat(driverProviders): Add TestObject and Kobiton as driverProviders
Add TestObject and Kobiton as driverProviders
Fixes
(a62a154)
fix(script): fix compile-to-es5 script (#4676)
make compile-to-es5 script rely on native es6-promise typing
(964baba)
fix(clientsidescript): avoid returning the value of test callback in waitForAngular (#4667)
The return value could be interpreted as an error by mistake in some situation
Also fix a wrong if-condition in error reporting
(83e2ba8)
fix(website): Locator by.name('field_name') (#4653)
(02746dd)
fix(browser): Add space after full stop in error message. (#4594)
Linkifiers interpret the ".If" at the end of the URL as part of the URL.
(7f968e0)
fix(direct): Use config's geckoDriver when specified (#4554)
This change makes the
firefox
capability more closely matchchrome
's. Thefirefox
capability was not looking for
config_.geckoDriver
likechrome
was.(f9df456)
docs(element): fix minor typo in element.ts (#4471)
(65f206e)
docs(website): updated reference from ignoreSynchronization to waitForAngularEnabled(false).
(#4632)
Dependencies
fix(circleCI): lock the currect version of all dependencies (#4669)
CircleCI was broken by the new release of gulp-clang-format and jasmine
v5.2.2
Compare Source
Fixes
(b3c7404)
Revert "fix(jasmine): Update Jasmine to support Node8 async/await (#4608)"
This reverts commit
5d13b00
.This commit is unnecessary now, revert this commit to avoid breaking changes in 5.2.1
(8e5ad1f)
fix(doc): remove unnecessary config in debugging doc/example (#4622)
v5.2.1
Compare Source
Features
feat(locators): Add support for regex in cssContainingText (#4532)
Fixes
fix(doc): update doc for testing with node 8 async/await and chrome inspector. (#4613)
doc(browser-support) improved Firefox documentation (#4553)
docs(page-objects.md): Refactor the existing Page Object example (#4576)
doc(tutorial): added example for element.getAttribute('value') to read text from an input (#4566)
Dependencies
Update to the latest blocking proxy (#4546)
Breaking Changes
(5d13b00)
fix(jasmine): Update Jasmine to support Node8 async/await (#4608)
Breaking change for TypeScript:
JasmineWD doesn't know anything about async/await, turns off JasmineWD if control flow was
disabled.
It will affect TypeScript tests that are using async/await and
a. miss some await keyword in the test.(Previously, this might cause the
test failed silently and be reported as pass), or
b. use Promise in jasmine expect function
Before
After
v5.2.0
Compare Source
Fixes
(f7e17f3)
fix(clientSideScripts): change protractor to support waiting for hybrid app (#4512)
(4b7cada)
fix(sauce): bring back sauceProxy as a configuration option (#4419)
(b87159b)
fix(website): fix all locator examples to use
element
overbrowser.findElement
(#4413)(768fd39)
fix(local): allow local driver provider to use gecko driver from config (#4412)
(c0b8770)
docs(website): fix issue 4246
(f79938e)
docs(plugins): add ng-apimock plugin to plugins.md
(ab1afb0)
fix(blockingproxy): Start bpRunner strictly after setupDriverEnv
(b85e7ee)
fix(npmignore): .map files in built directory cause stacktrace lines to nowhere Fixes #4371
(299fc8d)
docs(browser-support): Fixed incorrect example
(e5a5d59)
docs(frameworks) align cucumberOpts comments
(fe8c480)
docs(frameworks) update cucumber dry run option
(2e9acf5)
docs(plugins) add protractor-numerator plugin to plugins.md
(3f861ae)
By.js locator should accept functions
Dependencies
chore(release): update selenium-webdriverjs
v5.1.2
Compare Source
Features
(dd2ccbb)
feat(saucelabs): Add Sauce Labs protocol customization support
New option
sauceSeleniumUseHttp
available inprotractor.conf.js
If true, uses 'http' instead of 'https' to connect to Sauce Labs defined by
sauceSeleniumAddress
Fixes
(1a47076)
fix(ci): Use latest pip on CircleCI
(fd59c78)
fix(elementexplorer): Set script breakpoints with cross-platform safe paths.
Fixes #4011
(1250278)
fix(cli): Correctly parse list chromeOptions
Chromedriver requires that certain options always be passed as an array. Optimist passes
--single-option as a string instead of an array which is invalid. This ensures that we always pass
an array, even if a single option is passed via the cli.
Fixes #4050
(183cd80)
fix(browser): Fix browser.angularAppRoot()
By default, it wasn't returning anything. Now it returns a promise that resolves to
internalAngularAppRoot. Fixes #4233
(bd534fb)
fix: Add "stackTrace" option to allowedNames in cli.ts
This fixes a problem I encountered similar to #4196 - where
stackTrace
is listed as an optionbut an error is given saying it's an "unknown extra flag"
(8249167)
fix: export Runner, not just its type. (#4227)
(0eb5b76)
fix(navigation): ignore unknown JS errors in IE (#4149)
The
err
object doesn't have thecode
property any more (Selenium Server Standalone 3.3.1 +IEDriver win32 3.3.0), so we need a new way to detect those errors. See #841
(4752ad1)
chore(examples): Fix TSC issues with exampleTypescript (#4132)
Dependencies
chore(deps): Updating webdriver-manager and jasminewd2
v5.1.1
Compare Source
Features
(3edd62e)
feat(saucelabs): Add Sauce Labs HTTPS Support (#4071)
(29f975a)
feat(plugins): allow plugins to know which browser instance to run against (#4066)
Closes Forked browsers execute plugins incorrectly angular/protractor#4054
Dependencies
(9d69a81)
deps(typescript): use typescript@~2.0.0 (#4062)
Breaking Changes
is 'https' (previously used 'http'). The protocol is not configurable in this version.
v5.1.0
Compare Source
Blocking proxy
Blocking Proxy is a new experimental feature in Protractor 5 and is behind the
--useBlockingProxy
orblockingProxyUrl
. See thelib/config.ts#L100.
Other ways to start blocking proxy include using the
--highlightDelay
and--webDriverLogDir
flags See lib/config.ts#L501.This adds two options, both of which are implemented with Blocking
Proxy.
--webDriverLogDir
will create a readable log with timinginformation of webdriver commands in the specified directory.
--highlightDelay
will pause before clicking on elements or sending keys.While paused, the element that's about to be affected will be
highlighted.
Webdriver-manager
Webdriver-manager will now by default grab the latest versions of all binaries
(standalone, chromedriver, iedriver, gecko driver). Use the
--versions.(binary name)
to pin to a specific version. Selenium standalone3.0.1 has a bug which prevents it from working with any version of FireFox.
We have tested version 3.0.0-beta4 and know that it works with
FireFox 51, and we expect that the 3.0.2 release will also work.
TypeScript support
For jasmine users, in order to get all the type declarations that are used in
jasminewd2, you'll need to install
@types/jasminewd2
in addition to@types/jasmine
as dev dependencies.Features
(0cd156d)
feat(debugging): Add webdriver logging and highlight delay. (#4039)
This adds two options, both of which are implemented with Blocking
Proxy. --webDriverLogDir will create a readable log with timing
information of webdriver commands in the specified directory.
--highlightDelay will pause before clicking on elements or sending keys.
While paused, the element that's about to be affected will be
highlighted.
(3d98a16)
feat(config): Support setting
SELENIUM_PROMISE_MANAGER
flag via the config (#4023)Closes Support setting
SELENIUM_PROMISE_MANAGER
flag via the config angular/protractor#3691(4e40fb1)
feat(browser): chain promises in
browser.get
(#4017)Closes Chain promises together in
lib/browser.ts
angular/protractor#3904(33393ca)
feat(browser): chain some promises in
lib/browser.ts
+ return promise fromwaitForAngularEnabled
(#4021)Minor breaking change since
waitForAngularEnabled
no longer returns a booleanPart of #3904
Chaining
browser.get
has proved surprisingly complex, so I'll do that in a different PRAlso fixed a minor bug in
lib/clientsidescripts.js
while debuging(7cb9739)
feat(browser.ready): make
browser.ready
wait for all async setup work (#4015)Closes Enhance
browser.ready
angular/protractor#3900(b77cb92)
feat(restart):
browser.restart
should return a promise (#4008)Also allows
browser.restart
to work when the control flow is disabled, andfixes it for forked browsers.
Closes #3899 and #3896
Restarting forked browsers is broken angular/protractor#3896
(4a59412)
feat(angularAppRoot): Replace rootEl with browser.angularAppRoot() (#3996)
Replace browser.rootEl with browser.angularAppRoot(), which changes the root element in a promise
on the control flow. Note that browser.rootEl will immediately return the current value, but
browser.angularAppRoot() will return a promise that resolves during the next step in the control
flow.
Also update to BlockingProxy 0.0.3, which allows changing rootSelector.
(879aac6)
chore(blockingproxy): Allow using a pre-existing Blocking Proxy instance (#3970)
(bf123ad)
feat(elements): Add isPresent() to ElementArrayFinder. (#3974)
Bug Fixes
(f9bee84) fix(restart): preserve waitForAngularEnabled on restart and add promise chaining
I noticed I missed
waitForAngularEnabled
in #4037. This commit fixed that.While I was at it I fixed a minor error where the promises implicitly created by
setting
rootEl
andignoreSynchronization
weren't getting chained properly.Also fixed minor (so minor I think it was impossible to trigger) where
browser.plugins_ could be undefined.
(0b0c224)
fix(plugins): do not force ManagedPromise in plugins.ts (#4036)
(9c2274d)
fix(restart): preserve properties like
browser.baseUrl
upon restart (#4037)I also fixed a minor issue where
internalRootEl
wasn't being set when blocking proxy was beingused. I also just cleaned up our internal uses of
this.rootEl
.Closes #4032
(a20c7a7)
fix(element chaining): make element chaining work when the control flow is disabled (#4029)
Also added some tests to
spec/ts/noCF/smoke_spec.ts
double checking that the control flow is off(7481dee)
fix(cli): Make unknown flag check a warning instead of an error. (#4028)
(40bbeca)
fix(expectedConditions): Add tests and fix race conditions around visibility (#4006)
Add test cases to reproduce the missing element race conditions possible in
expected condition methods
visibilityOf
,textToBePresentInElement
,textToBePresentInValue
andelementToBeClickable
.Add error handler
falseIfMissing
to all expected conditions that dependon the presence of an element.
Expected conditions check the presence of an element before other checks,
but when an element is removed exactly in the moment after the
isPresent
and before
isDisplayed
invisibilityOf
the condition used to fail.This solution does not handle missing elements in (
isEnable
,isDisplayed
,isSelected
) and focused only on expected conditions (see #3972)This problem was also referenced in #3578 and #3777
(5856037)
fix(cli): Allow frameworks to specify flags they recognize. (#3994)
Fix for #3978.
Our initial plan to allow setting --disableChecks with an environment variable is insufficient,
since the custom framework isn't even require()'d until after the config is parsed. This moves the
unknown flag check into the runner, and gives frameworks a way to specify extra flags they accept.
(e68dcf1)
fix(driverProviders): Check config in the right place. (#3991)
(eb89920)
fix(driverProviders): Handle promise rejection when starting selenium (#3989)
Fixes #3986. Also error if jvmArgs isn't an array.
(8d2fc07)
chore(browser): deprecate
browser.getLocationAbsUrl()
. (#3969)Closes #3185
(15a1872)
fix(firefox): Fix directConnect for Firefox 51+ (#3953)
(81f56a4)
fix(cli): display disableChecks option in extra flags error message (#3964)
(6a4dc7a)
fix: no longer use es6 let statement (#3963)
let
modifier.This can break Protractor on browsers, which doesn't support those statements.
(528338c)
fix(expectedCondition): fix NoSuchElementError in visibilityOf due to a race condition (#3777)
Handle NoSuchElementError in the expected condition visibilityOf, which occurred when
an element disappears between the isPresent() and isDisplayed() check.
Dependencies
(5899b67)
deps(update): update webdriver-manager to ^12.0.1 (#4042)
Running
webdriver-manager update
will now by default grab the latestversions of all binaries (standalone, chromedriver, iedriver, gecko
driver). You can continue to pin to a specific versions using the
command line option. Example
webdriver-manager update --versions.chrome 2.20
.As of this release the latest versions are:
below on Firefox support.
A note on FireFox support: Selenium standalone 3.0.1 has a bug which prevents it from working
with any version of FireFox. We have tested version 3.0.0-beta4 and know that it works with
FireFox 51, and we expect that the 3.0.2 release will also work.
closes #4033
(cd084a0)
deps(jasmine): update jasmine to ^2.5.3 (#3960)
v5.0.0
Compare Source
This version includes big changes around upgrading to selenium-webdriver 3.0.x.
See the selenium-webdriver changelog.
For the 5.0.0 release, we are still using the selenium standalone server 2.53.1
and recommend using Firefox 47. Firefox 48+ currently is not supported.
Breaking Changes
Minimum node version is now 6.9.x.
When testing with Firefox 47, use the capability option
marionette: false
to use the legacy Firefox driver.
Before:
After:
We moved
@types/jasmine
to a devDependency. This means that JasmineTypeScript users will need to include the
@types/jasmine
as a projectdependency. This is to avoid conflicts for users that prefer mocha typings.
After:
Selenium-webdriver methods removed:
WebDriver.prototype.isElementPresent
,WebElement.prototype.getRawId
,WebElement.prototype.getInnerHtml
, andWebElement.prototype.getOuterHtml
.Before:
After:
Selenium-webdriver
ErrorCodes
have been removed.Adding cookies have been changed:
Before:
After:
Removed
protractor.wrapDriver()
.You can no longer use
repl
command from withinbrowser.pause()
. Instead,use
browser.explore()
to directly enter therepl
.Sending flags that are not recognized by the CLI throws an error. Since flags
are a subset of all configuration options, these errors can be silenced with
--disableChecks
.Auto-detection of the root element. This is a breaking change because it
changes the default root element behavior and removes the
config.useAllAngular2AppRoots
flag. Modern angular apps nowdefault to using all app hooks, and ng1 apps now check several places, notably
the element the app bootstraps to.
sauceProxy
configuration field has been removed. UsewebDriverProxy
instead.
Before:
After:
Features
(ec93c4a)
chore(cli): breaking change throw errors on unknown flags (#3921)
Unknown flags are options sent that is unrecognized by the CLI. For users that
encounter this error but would like to silence it, use:
--disableChecks
.closes #3216
(bc58332)
feat(rootEl): breaking change auto-detect the root element better (#3928)
This is a breaking change because it changes the default root element behavior
and removes the
config.useAllAngular2AppRoots
flag. Modern angular apps nowdefault to using all app hooks, and ng1 apps now check several places, notably
the element the app bootstraps to.
closes #1742
(604fdbf)
cleanup(config): breaking change Remove redundant sauceProxy config (#3868)
Removes the
sauceProxy
config field, and useswebDriverProxy
when creatingthe SauceLabs client.
(9465b9f)
feat(mobile): add extended wd commands for appium (#3860)
Also had to make some minor changes to the website to handle longer inheritance
chains
Closes Support Appium's additional WebDriverJS commands angular/protractor#1940
(0e26b21)
feat(blockingproxy): Add synchronization with BlockingProxy. (#3813)
This adds support for BlockingProxy behind the flag --useBlockingProxy.
If set, the driver providers will start a proxy during their setup phase,
passing the selenium address to the proxy and starting a webdriver client
that talks to the proxy.
Starting a proxy for each driver provider isn't strictly necessary. However,
when we run with multiple capabilities it's easier to handle the logging if
each Protractor instance has it's own proxy.
Known issues:
mucking around in Selenium internals, but this probably changed for Selenium
3.0 and I doubt it's worth figuring out until we upgrade.
(ca4f1ac)
chore(driverProviders): add warnings to extra driver provider parameters (#3873)
closes #1945
(681b54a)
refactor(browser): Remove protractor.wrapDriver() breaking change (#3827)
Before:
Users could create their own selenium driver instance and enable Protractor on
it like so:
Over the years, wrapDriver() has become increasingly broken as Protractor
needs extra configuration options that wrapDriver() doesn't set.
After:
This method is removed. If users need a new browser instance, they can
use
browser.forkNewDriverInstance()
.(86fd569)
feat(ngUpgrade): Auto detect ngUpgrade apps and make the ng12Hybrid flag
unnecessary for most users (#3847)
Bug fixes
(de153e7)
fix(launcher): running getMultiCapabilities should reject on errors (#3876)
closes #3875
(1345137)
fix(isElementPresent): for un-wrapped
WebElement
s,browser.isElementPresent
was broken (#3871)
Closes #3864
(4af3b2e)
fix(element): Fix typing of ElementFinder.then (#3835)
Type
then
as optional on ElementFinder.Dependencies
(4d87c9c)
deps(update): update tslint and @types/selenium-webdriver (#3941)
closes #3939
(7376708)
deps(tslint): set tslint to ~4.2 (#3938)
(cb38ed0)
Refactor element explorer to work with selenium-webdriver 3 (#3828)
This implementation now relies mostly on promises explicitly, so the control
flow is only used to add one large task to the queue. This should pave the way
for the eventual removal of the control flow, as well as getting element
explorer to work immediately.
BREAKING CHANGE
You can no longer use the
repl
command from withinbrowser.pause()
. Instead,use
browser.explore()
to directly enter the repl.(8196059)
chore(dependency): switch to webdriver-manager 11.1.0 and remove
--versions.chrome 2.26
from circle.yml (#3865)(397bf65)
deps(update): move @types/jasmine to devDependencies (#3795)
closes #3792
(a3e8b43)
deps(selenium-webdriver): upgrade to selenium 3 (#3781)
Please see the selenium-webdriver changelog
Removed method
WebDriver.prototype.isElementPresent
Removed method
WebElement.prototype.getRawId
Removed
getInnerHtml
andgetOutterHtml
Dependency required for upgrade: use
jasminewd2@​0.1.0
.Selenium-webdriver requires node version 6+, updating travis and circle yml
to use node 6 and 7.
Use
instanceof
selenium-webdriver error instead of error code.Selenium-webdriver error codes have been deprecated.
Use executor with selenium-webdriver from
lib/http
. Deferred executor hasbeen deprecated.
Fix quitting
driverProviders
. When callingwebdriver.quit
, the controlflow is shutdown and will throw an error.
Driver provider for direct connect has been modified to use
ServiceBuilder
and to call the
Service
tocreateSession
Note: Since this upgrade is still using FF 47, direct connect for Firefox is
required to pass "marionette: false" in the capabilities. If you do not pass
marionette to false, it will look for gecko driver in the PATH.
Added a TODO to support FF after 48+ with direct connect and gecko driver.
Updated
browser.manage().addCookie('testcookie', 'Jane-1234');
to usebrowser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});
Updated debug commons for breakpoint updated to selenium-webdriver
lib/http
line 432.For mocha tests,
selenium-webdriver/testing
uses the globalit
andcannot be reassigned as Protractor's global
it
. Some code has beencopied / modified to
lib/frameworks/mocha
to make this work.Capabilities for Firefox 47 requires setting marionette to false.
Setup still requires selenium standalone server 2.53.1 for Firefox tests.
Firefox version used is 47.
Using selenium standalone server 3, with Firefox 48+ tests fail with gecko
driver still do not work.
Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a
single test but after it quits, selenium standalone no longer works with
firefox. When firefox 48 exists, logs show the following:
(eb31c9c)
deps(types): update @types/selenium-webdriver dependency (#3886)
Fixes issue #3879 and adds the protractor.Key.chord method
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.