Page MenuHomePhabricator

ProveIt gadget test causes page.feature etc. to fail in Chrome
Closed, InvalidPublic

Description

ProveIt floats over Save

The ProveIt tool floats on top of the wikitext editor controls and makes the test fail like so attempting to click 'Save page':

$ bundle exec cucumber features/page.feature:38
Using the default profile...
....F------

(::) failed steps (::)

unknown error: Element is not clickable at point (259, 764). Other element would receive the click: <div id="tabs" class="ui-tabs ui-widget ui-widget-content ui-corner-all">...</div>
  (Session info: chrome=30.0.1599.66)
  (Driver info: chromedriver=2.3,platform=Linux 3.2.0-54-generic x86_64) (Selenium::WebDriver::Error::UnknownError)
./features/step_definitions/page_steps.rb:9:in `/^I click Save page button$/'
./features/step_definitions/page_steps.rb:51:in `/^I create the page to be moved$/'
features/page.feature:38:in `And I create the page to be moved'

Failing Scenarios:
cucumber features/page.feature:35 # Scenario: Move existing page dialog

1 scenario (1 failed)
10 steps (1 failed, 6 skipped, 3 passed)
0m36.042s

Version: unspecified
Severity: enhancement

Attached:

proveit_save.png (256×1 px, 31 KB)

Details

Reference
bz55751

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 2:37 AM
bzimport set Reference to bz55751.
bzimport added a subscriber: Unknown Object (MLST).

tplavcic wrote:

What is the best possible solution for this?
Is it to implement something like Page Down keypress before clicking the save button (user would probably scroll up-down to see where are the buttons) or something else?

We could enable the gadget in a "before" hook before each ProveIt scenario and disable it an "after" hook after each scenario, so the gadget is active only when the tests for it are running.

That screenshot doesn't show ProveIt blocking the save button.

It could be a bug in the test, or perhaps it needs a moment to position ProveIt before you do the save.

Created attachment 13521
ProveIt really floats over Save

This is arguably a bug in ChromeDriver. This part of the WebDriver W3C standard is being discussed as we speak, actually. Firefox is liberal about what can be clicked, Chrome is not.

Attached:

Screen_shot_2013-10-18_at_8.35.30_AM.png (234×764 px, 34 KB)

(In reply to comment #1)

What is the best possible solution for this?
Is it to implement something like Page Down keypress before clicking the save
button (user would probably scroll up-down to see where are the buttons) or
something else?

I think I would like to just run the test for Firefox and not for Chrome. (And see what happens with Internet Explorer)

Change 91180 had a related patch set uploaded by Cmcmahon:
don't run the ProveIt test for Chrome because of Bug 55751

https://gerrit.wikimedia.org/r/91180

Change 91180 abandoned by Cmcmahon:
don't run the ProveIt test for Chrome because of Bug 55751

Reason:
mistake

https://gerrit.wikimedia.org/r/91180

Change 91182 had a related patch set uploaded by Cmcmahon:
ProveIt gadget causes Page test to fail in Chrome Bug 55751

https://gerrit.wikimedia.org/r/91182

Change 91182 merged by Cmcmahon:
ProveIt gadget causes Page test to fail in Chrome Bug 55751

https://gerrit.wikimedia.org/r/91182

It hasn't been fixed, right?

My understanding was just that you stopped running the tests for now. So how about just marking it lowest priority?

Closing since this seems to be fixed. Please reopen if the problem is not fixed.

I checked with Chris. They are still not running, and this is not fixed.

Stopping them from running was just a workaround.

Well, if move page is not running, if anything that means ProveIt would not conflict.

But it seems a better solution (if we wanted to restart ProveIt tests) would be T90964: Create pool of user accounts on beta cluster for browser test builds in Jenkins, so there could be a ProveIt user that ran ProveIt tests without affecting other tests running as different users.