aboutsummaryrefslogtreecommitdiffstats
path: root/tests/drone-run-php-tests.sh
diff options
context:
space:
mode:
authorDaniel Calviño Sánchez <danxuliu@gmail.com>2021-04-18 22:21:38 +0200
committerDaniel Calviño Sánchez <danxuliu@gmail.com>2021-04-19 16:35:11 +0200
commit4b376a107ba4f30ca5d5db559f09685378bb8730 (patch)
treeb07794958924e2aa6296f91771f2a476bb4b54be /tests/drone-run-php-tests.sh
parent9e1246eba5980446bf300b6f4bf58eb3be829843 (diff)
downloadnextcloud-server-4b376a107ba4f30ca5d5db559f09685378bb8730.tar.gz
nextcloud-server-4b376a107ba4f30ca5d5db559f09685378bb8730.zip
Add automatic handling of "ElementNotInteractable" exceptions
In the WebDriver protocol, when a command fails because it can not interact with the target element, an "element not interactable" error is generated. It can be a transitive issue (for example, due to an animation), so when the error is received the command should be tried again, just like done, for example, with "ElementNotVisible" exceptions. However, the last version of the "instaclick/php-webdriver" library compatible with the Selenium Driver of Mink did not support yet that WebDriver error. And even if Chrome is run using the old protocol an unknown "element not interactable" error can be received anyway in some cases. When an unknown error is received by the "instaclick/php-webdriver" library it is thrown as a generic Exception so, until the library can be updated, the message of generic exceptions is checked and the command is retried if it matched. For the time being "element not interactable" errors are handled like "ElementNotVisible" exceptions; this may need to change once the error is better understood. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Diffstat (limited to 'tests/drone-run-php-tests.sh')
0 files changed, 0 insertions, 0 deletions