Project

General

Profile

Actions

action #123076

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

Unify qam-yast_self_update+15@uefi for sle15sp3 and sle15sp4 using single test module for registration

Added by hjluo almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2023-01-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We have a quick PR 16226 to fix the 15sp3 ltss issue, for we don't need ltss for sles15sp4. We use conditional yaml there for the time being. The flow is different depending on if we have ltss or not in a product.

So we need to unify qam-yast_self_update+15@uefi for sle15sp3 and sle15sp4 in one test module without conditional Schedule.
For doing that we need to develop a single module which is able to react to those different flows

The common test case when we have ltss and when we don't have it is that we want to register the system with a list of addons (for now we can depends on settings for that with comma-separate list of modules).

We could have some method like register_extension_and_modules and fix each flow with distri provided should do the trick.
Then we will unify in one test module:
installation/module_registration/register_extensions_and_modules
installation/module_registration/add_additional_regcodes
installation/module_registration/import_untrusted_gnpupg_key
installation/module_registration/add_ltss_regcode

No need to depend anymore of ltss setting for the flow of screen.

In that case we will not depend on the setting, we will have single place to change this.

Acceptance criteria

AC1: Use distribution provider in libyui-rest-api framework to perform different actions for registration depending on ltss or not.
AC2: Add code if need to make simple review if setting in openQA doesn't match the flow for both cases.
AC3: Unify in single yaml schedule aforementioned test suite.

Actions

Also available in: Atom PDF