[Webkit-unassigned] [Bug 188118] [GTK] Many WebDriver tests are failing

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=188118

--- Comment #8 from Michael Catanzaro <mcatanzaro at igalia.com> ---
Mmmm, the WebDriver expectations are not cooperating. I'm gcurrently sitting at:


Expected to fail, but passed (3)
  imported/w3c/webdriver/tests/close_window/close.py::test_close_last_browsing_context
  imported/w3c/webdriver/tests/maximize_window/maximize.py::test_fully_exit_fullscreen
  imported/w3c/webdriver/tests/minimize_window/minimize.py::test_fully_exit_fullscreen


All of the above have flaky expectations, just like for API tests. Perhaps the test runner is not able to handle multiple expectations? The same syntax works for API tests.


Unexpected failures (4)
  imported/selenium/py/test/selenium/webdriver/common/alerts_tests.py::testShouldHandleAlertOnPageBeforeUnload[WebKitGTK]
  imported/selenium/py/test/selenium/webdriver/common/page_load_timeout_tests.py::testClickShouldTimeout[WebKitGTK]
  imported/selenium/py/test/selenium/webdriver/common/page_load_timeout_tests.py::testClickShouldTimeout[WebKitGTK]
  imported/selenium/py/test/selenium/webdriver/common/window_tests.py::test_should_fullscreen_the_current_window[WebKitGTK]


Ditto, except for that last test, which has just a FAIL expectation. I'll try removing the "[WebKitGTK]" from the end of the expectations and see if it makes any difference.


Unexpected timeouts (1)
  imported/w3c/webdriver/tests/actions/special_keys.py::test_webdriver_special_key_sends_keydown[F5-expected55]


This one is skipped, and has been for ages, so at least this one should not be my fault. :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180727/143df905/attachment.html>