An in-range update of nightwatch is breaking the build π¨
Closed this issue Β· 1 comments
The devDependency nightwatch was updated from 1.1.13
to 1.2.1
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
nightwatch is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v1.2.1
New commands
Added several new commands in-line with the W3C Webdriver API:
Improvements
waitForElementVisible
doesn't throw an error anymore if the element cannot be found - #2148- Addedw W3C Webdriver API compatibility support for
.timeouts()
command; - Added
suppressNotFoundErrors
option for element selector properties to enable suppressingNoSuchElement
errors when element is not found for commands such as.click()
or.getText()
etc.
Fixes
Commits
The new version differs by 27 commits.
dfe1681
1.2.1
324a8cf
Updated unit test for maximize
caed58d
Merge branch 'master' of github.com:nightwatchjs/nightwatch
6bb7a2d
Update actions.js
2a064e6
fix maximize a POST command
68bdada
1.2.0
c795d08
fixed a typo in suppressNotFoundErrors option
d7e4b82
Updated .timeouts() to be compatible with W3C Webdriver API; api docs updates
1efabca
Merge branch 'master' of github.com:nightwatchjs/nightwatch
7f21b96
Bump lodash from 4.17.11 to 4.17.15 (#2172)
d0e2411
Merge branch 'iberdinsky-skilld-2155-possible_element_selector_fix'
142f84f
Merge branch '2155-possible_element_selector_fix' of https://github.com/iberdinsky-skilld/nightwatch into iberdinsky-skilld-2155-possible_element_selector_fix
81c4eee
fix #2168 - added window related W3C commands
99b47c0
updated condition. in object 2155
bcdf0d1
updated the check for possible element selector arguments for page object commands
There are 27 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After pinning to 1.1.13 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.