action #39908

[functional][u] Make pkcon / packagekit installation test more explicit

Added by okurz over 1 year ago. Updated 1 day ago.

Status:WorkableStart date:17/08/2018
Priority:NormalDue date:
Assignee:-% Done:


Category:New testEstimated time:42.00 hours
Target version:SUSE QA tests - Milestone 31



On font changes like introduced by
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 issues

Related to openQA Tests - action #36691: [sle12sp4][desktop] Implement test cases for gnome-packag... New 01/06/2018


#1 Updated by okurz over 1 year ago

  • Related to action #36691: [sle12sp4][desktop] Implement test cases for gnome-package-kit/packagekit. added

#2 Updated by mgriessmeier 1 day ago

  • 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

Also available in: Atom PDF