"element not interactable" exception in webUI tests

[phil-davis]

e.g. https://drone.owncloud.com/owncloud/core/15759/787

        Exception: element not interactable
          (Session info: chrome=72.0.3626.119)
          (Driver info: chromedriver=2.46.628388 (4a34a70827ac54148e092aafb70504c4ea7ae926),platform=Linux 4.4.0-142-generic x86_64) in /drone/src/vendor-bin/behat/vendor/instaclick/php-webdriver/lib/WebDriver/Exception.php:144

It seems to be intermittent but happening when testing the user management page of the UI.

Most of the time each test scenario passes on a 2nd run. Sometimes the 2nd try fails and so we notice a I fail result.

Needs investigation.

[ownclouders]

GitMate.io thinks possibly related issues are #22492 (test), #31579 (test), #22485 (test), #24121 (Clean/Fix exceptions when running integration tests), and #32842 (webUI test comments).

[phil-davis]

@PVince81 I added this to the next sprint, because it is happening quite a lot.

[phil-davis]

• Phase 1: waiting for settings menu to animate open on user management page
  Wait for settings menu animation on users page owncloud-archive/user_management#158
  [stable10] Wait for settings menu animation on users page #34720
• monitor drone runs to see what else is failing
• write some smarter Jquery to loop and wait until the settings menu has finished animating (maybe?) edit,update: decided not to do this

[individual-it]

looks like its working stable now.
to get rid of the sleep(1) we could check the style of the box.
when its hidden it is: display: none

During the transition is has a lot of other settings:

and when finished it only has display: block;

is it worth the effort?

[phil-davis]

Having detailed knowledge of the "workflow" of styles, DOM elements,... baked into test code will make the tests more brittle when people adjust the styles of stuff. So maybe that will be just as annoying as having sleep(1)?

[individual-it]

one could argue that its knowledge of how jQuery does the animation. But I agree, in this case a sleep(1) might be alright.
deleting the ToDo in the code with reference to this issue and closing the issue?

[phil-davis]

owncloud-archive/user_management#170 removes the "ToDo"