Project

General

Profile

action #109737

Updated by livdywan almost 2 years ago

## Observation 

 openQA test in scenario opensuse-15.3-DVD-Updates-x86_64-gnome@64bit-2G fails in 
 [chromium](https://openqa.opensuse.org/tests/2287780/modules/chromium/steps/19) 
 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](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD-Updates&machine=64bit-2G&test=gnome&version=15.3) 

 ## 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

Back