action #39908
closed
[functional][u] Make pkcon / packagekit installation test more explicit
Added by okurz over 5 years ago.
Updated over 3 years ago.
Target version:
SUSE QA - Milestone 31
Estimated time:
42.00 h (Total: 84.00 h)
Description
Motivation¶
On font changes like introduced by
https://bugzilla.opensuse.org/show_bug.cgi?id=1105181
many openQA tests fail and some even in very obscure way because the previous needles for an older font do not match anymore in an annoying way, hidden behind a job timeout or that the screen lock kicks in. Problem is that we use "pkcon install" here and need to check for both the exit status as well as for needles to handle the policykit based authentication windows. We thought about executing that only in an explicit test module and using zypper otherwise.
However, that would not reduce the number of needles necessary to maintain, only make it more explicit what is happening
Acceptance Criteria¶
AC1: seperate testmodule to test pkcon is added
AC2: all current scenarios which use pkcon are adapted to use zypper_call instead
- Related to action #36691: [sle12sp4][desktop] Implement test cases for gnome-package-kit/packagekit. added
- Description updated (diff)
- Category changed from Enhancement to existing tests to New test
- Status changed from New to Workable
- Target version changed from future to Milestone 31
- Estimated time set to 42.00 h
- Due date set to 2020-07-03
- Start date changed from 2018-08-17 to 2020-07-03
Grund: Änderung an zugehörigem Ticket: #68621
- Related to action #59241: [sle][functional][u] test fails in libqt5_qtbase - pkcon giving a false positive added
- Status changed from Workable to In Progress
- Assignee set to zluo
take over for AC2: all current scenarios which use pkcon are adapted to use zypper_call instead
check where 'pkcon install' is used and then think about replace it
ready to review or merge.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF