action #66149
closed
[desktop][u] seahorse 3.36 needs test adjustments
Added by dimstar about 4 years ago.
Updated almost 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Description
Observation¶
The test needs to be adjusted to interact properly with seahorse 3.36
seahorse was previously opened at the main panel. Since it fails, it is opened in the sub-panel "GPG keys". (product bug?)
Acceptance criteria¶
- AC1: seahorse passes or soft-fail on a product bug
Suggestions¶
- Investigate why seahorse opens in the sub-panel "GPG keys" and figure out if it is a test bug or a product bug
Reproducible¶
- Fails in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_gnome@64bit
- Current occurrence: 20200815
- Last good: 20200329
- latest
Related issues
1 (1 open — 0 closed)
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1264772
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1279564
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1294372
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1312450
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1328349
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1339737
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Subject changed from seahorse 3.36 needs test adjustments to [desktop][u] seahorse 3.36 needs test adjustments
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
http://10.162.23.47/tests/7993#step/seahorse/14
I find out: seahorse is locked and it requires an unlock, this is difference than it on sled. At least this is new issue.
The problem is after Unlock it doesn't display entries of passwords (Login), Keys(GPG Keys), Certificates (Default Trust).
I think I can report this as bug for now.
- Status changed from In Progress to Resolved
- Related to action #89422: [opensuse] test fails in seahorse starting with keyring lock screen for ppc64le added
Also available in: Atom
PDF