action #106470
Updated by mkittler about 2 years ago
Since some of openQA's Selenium-based tests are affected¹ I've been creating this ticket to keep track of the supposedly upstream bug in ChromeDriver 98.0.4758.80. The relevant upstream ticket is https://bugs.chromium.org/p/chromedriver/issues/detail?id=3999 and the problem is currently only mentioned in comments on https://bugs.chromium.org/p/chromedriver/issues/detail?id=2269. One can easily workaround the issue via ``` sudo zypper in --oldpackage http://download.opensuse.org/history/20220206/tumbleweed/repo/oss/x86_64/chromedriver-97.0.4692.99-1.1.x86_64.rpm http://download.opensuse.org/history/20220206/tumbleweed/repo/oss/x86_64/chromium-97.0.4692.99-1.1.x86_64.rpm ``` and the CI is not affected yet as well. If the problem isn't fixed by upstream soon we can consider implementing a workaround on our side. I've already created one for the fullstack tests as it simplifies the code there anyways (see https://github.com/os-autoinst/openQA/pull/4499/commits/bf611dd47b52e9a73f67f9cdfc968ba8c495cb25). We could do the same for other tests (using the JavaScript DOM API to set the form element value directly). --- ¹ The error is: `sendKeysToElement: unknown error: Cannot construct KeyEvent from non-typeable key`