action #33625
closed[opensuse][functional][u]test fails in seahorse - assert_and_click right for set_as_default is not working
0%
Description
checked manually and found out that mouse click right for showing context menu "set as default" is not working.
set as default should be displayed on screen which is not the case atm.
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_gnome@64bit fails in
seahorse
Reproducible¶
Fails since (at least) Build 20170531
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 7 years ago
- Subject changed from [opensuse][functional]test fails in seahorse - assert_and_click right for set_as_default is not working to [opensuse][functional][fast][u]test fails in seahorse - assert_and_click right for set_as_default is not working
- Due date set to 2018-03-27
- Target version set to Milestone 15
Updated by zluo almost 7 years ago
- Status changed from New to Workable
- Assignee set to zluo
take over...
Updated by zluo almost 7 years ago
- Status changed from Workable to In Progress
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2018-03-27 to 2018-04-10
- Status changed from In Progress to Feedback
setting to feedback, PR is waiting for merge
Updated by okurz almost 7 years ago
- Subject changed from [opensuse][functional][fast][u]test fails in seahorse - assert_and_click right for set_as_default is not working to [opensuse][functional][u]test fails in seahorse - assert_and_click right for set_as_default is not working
@zluo please make sure to find an expected result first. In the PR you mentioned "sporadic". Can you elaborate on that?
Updated by zluo almost 7 years ago
- Status changed from Feedback to In Progress
The most test runs didn't have this problem. About 5 of 100 failed...
Updated by okurz almost 7 years ago
- Status changed from In Progress to Resolved
ok, with this low failure ratio a local verification is very expensive to conduct. I merged the PR in good hope. If the test still fails now after 60 seconds it's probably another problem, e.g. product issue.