Project

General

Profile

Actions

action #109737

closed

[opensuse][sporadic] test fails in chromium due to lost characters when typing in the address bar size:M

Added by okurz almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-04-09
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-15.3-DVD-Updates-x86_64-gnome@64bit-2G fails in
chromium
due to lost characters when typing in the address bar which triggers an unexpected consent dialog shown for the page google.com instead of the expected "about" dialog.

The problem is triggered by the test API command

enter_cmd "chrome://version ";

which in some cases is not correctly typed. For example in https://openqa.opensuse.org/tests/2287780#step/chromium/19 it can be seen that a google search for "chrion" is conducted, likely because only some characters of "chrome://version " where typed, ending up with just the first three "chr" plus the last three (with our without the following space) "ion".

Acceptance criteria

  • AC1: Chromium tests no longer fail sporadically

Reproducible

Fails sporadically. In https://openqa.opensuse.org/tests/2287780#next_previous I find a fail rate of roughly 3%.

Expected result

The test should ensure stable typing in the browser address bar or check for correct typing to prevent going to google at all or foresee the consent dialog. https://openqa.opensuse.org/tests/2287076#step/chromium/19 shows how the about dialog looks like when there is no consent dialog for google because in https://openqa.opensuse.org/tests/2287076#step/chromium/17 search.opensuse.org is shown.

Further details

Always latest result in this scenario: latest

Suggestions

  • Type every single character very slowly
  • Type first n(=10) characters slowly
  • Switch off autocomplete suggestions in the URL
  • If nothing works, just type all characters slowly again

Related issues 7 (2 open5 closed)

Related to openQA Tests - action #107632: [qe-core][leap][sporadic] Fix chromium test failing due to dropped keysRejectedzluo

Actions
Related to openQA Project - coordination #109740: [epic] Stable os-autoinst unit tests with good coverageResolvedokurz2021-06-30

Actions
Related to openQA Project - action #116554: Make sleeping time in "no_wait" scenarios consistent size:MResolvedmkittler2022-09-14

Actions
Related to openQA Project - action #110542: Try to mitigate "VNC typing issues" with disabled key repeatResolvedokurz2022-05-02

Actions
Related to openQA Tests - coordination #43889: [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakesBlocked

Actions
Copied to openQA Infrastructure - action #113800: Setup o3 to run rootless containers on worker hostsNew2022-04-09

Actions
Copied to openQA Project - action #114412: Add support for "wait_screen_change" with "no_wait" option to allow to use on cases like "wait for every character to be typed" size:MResolvedmkittler2022-09-16

Actions
Actions

Also available in: Atom PDF