Project

General

Profile

Actions

action #32845

closed

[qam] test fails in firefox_passwd - pwd change confirmation window hinders test from proceeding

Added by osukup about 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2018-03-07
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

unexcepted window about change of master password ..

openQA test in scenario sle-12-SP3-Desktop-DVD-Updates-x86_64-qam-regression-firefox@64bit fails in
firefox_passwd

Reproducible

Fails since (at least) Build 20180306-2

Expected result

Last good: 20180306-1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by vsvecova almost 6 years ago

  • Subject changed from [qam] test fails in firefox_passwd to [qam] test fails in firefox_passwd - pwd change confirmation window hinders test from proceeding

Still occasionally happening.

The test opens about:preferences on line 70 and wants to click the security icon, but cannot find it because there is still the password change confirmation window, which was supposed to be closed earlier, but wasn't (line 38-41 of the code). The window is focused and the security icon is therefore greyed out.

Actions #2

Updated by vsvecova almost 6 years ago

  • Assignee set to bfilho
Actions #4

Updated by bfilho almost 6 years ago

  • % Done changed from 0 to 100

I was having trouble trying to identify the issue because I was mistakenly thought that some part of the code was being skipped, but the behaviour found in the runs with the issue. I was also not able to reproduce the issue and the logs from previous runs were not available anymore in the servers.

Working with pcervinka, he pointed out that the issues was not happening from April 09 2018

It was found later that the previous poo #28291 had already addressed the problem with the following commit https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/c000f37a71a9afdbaae2e7747cd40c3ecd1fe610
accounting for the difference in the script lines that had effectively run since the commit was made.

Actions #5

Updated by bfilho over 5 years ago

  • Status changed from New to In Progress
Actions #6

Updated by bfilho over 5 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF