Closed
Bug 1470667
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 11638 - Correcting expected error response in WebDriver element_click test
Categories
(Testing :: geckodriver, enhancement, P4)
Testing
geckodriver
Tracking
(firefox63 fixed)
RESOLVED
FIXED
mozilla63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 11638 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/11638 Details from upstream follow. Jim Evans <james.h.evans.jr@gmail.com> wrote: > Correcting expected error response in WebDriver element_click test > > Test should expect the "element not interactable" error state, not the nonexistent "element not visible".
Assignee | ||
Comment 1•6 years ago
|
||
PR 11638 applied with additional changes from upstream: 3172a6c9ef2b21818a0658bb17f58b826bc07971
Assignee | ||
Updated•6 years ago
|
Component: web-platform-tests → geckodriver
Assignee | ||
Comment 2•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=57e579cd36ca79a02d52f8139bb3f8e45ff5e83f
Assignee | ||
Comment 3•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=14eacafa1e801fb1f9806f898cf602e1d04aecf7
Assignee | ||
Comment 4•6 years ago
|
||
Ran 1 tests and 6 subtests OK : 1 PASS : 5 FAIL : 1 New tests that have failures or other problems: /webdriver/tests/element_click/interactability.py test_element_not_visible_overflow_hidden: FAIL
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/ecaf326faf60 [wpt PR 11638] - Correcting expected error response in WebDriver element_click test, a=testonly
Comment 6•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ecaf326faf60
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•