Project

General

Profile

Actions

action #122905

closed

coordination #121858: [epic] Automation of YaST in Container

Automate Software Repositories in ALP Staging

Added by JERiveraMoya over 1 year ago. Updated 4 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2023-01-10
Due date:
% Done:

0%

Estimated time:

Description

Motivation

For staging we test yast2 repositories in a container for the actions related with adding staging repo.

The sequence of steps in the test could go like this:

  1. Open yast2 repositories in container (see additional information)
  2. Press Add
  3. Press Next (no need for clicking on Specify URL as it is default)
  4. Type Repository Name: Staging_$stage (we can get $stage from get_required_var("STAGING"))
  5. type URL: https://download.opensuse.org/repositories/SUSE:/ALP:/Staging:/$stage/images/repo/ALP-0.1-x86_64-Media1/ (it is not multi-architecture so we can hardcode it)
  6. Press Next
  7. Press Trust on Import Untrusted GnuPG Key Popup
  8. Select row in table with Name "Staging_$stage"
  9. Set lower number for priority to 90
  10. Refresh all enabled repos
  11. Check repo is enable with the most simple validation (let's put aside some libraries we have to do complex validation, it isn't worth): zypper lr --show-enabled-only --priority | grep Staging_B.*90

Scope

Only x86_64
Staging Job group: https://openqa.opensuse.org/tests/overview?groupid=105

Acceptance criteria

AC1: Create new test suite in staging with new test module providing the addition of staging repo via yast2 repositories in a container
AC2: Automate with libyui-rest-api using POM (using directly Pages in the test, without Controllers)
AC3: Implement One Page Object as appear to user as only one page
AC4: Focus on readability of the test (no comments required in general)

Additional information

We will access directly to the module (via control center libyui-rest-api doesn't work due to bsc#1206929):
YUI_HTTP_PORT=9999 YUI_HTTP_REMOTE=1 YUI_REUSE_PORT=1 podman container runlabel run registry.opensuse.org/suse/alp/workloads/tumbleweed_containerfiles/suse/alp/workloads/yast-mgmt-ncurses-test-api:latest repositories
In the future we can consider additional checks or action with this screen, but in case of staging needs to be something very solid.

Take a look to the example we have for POM without controllers at the moment:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16072/files

Actions #1

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #2

Updated by JERiveraMoya over 1 year ago

  • Parent task set to #121858
Actions #3

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #4

Updated by JERiveraMoya over 1 year ago

  • Tags deleted (qe-yam-refinement)
  • Status changed from New to Workable
Actions #5

Updated by JERiveraMoya about 1 year ago

  • Tags set to yam
  • Target version deleted (Current)
Actions #6

Updated by JERiveraMoya about 1 year ago

  • Tags changed from yam to qe-yam-refinement
Actions #7

Updated by JERiveraMoya about 1 year ago

  • Target version set to Current
Actions #8

Updated by JERiveraMoya about 1 year ago

  • Target version deleted (Current)
Actions #9

Updated by JERiveraMoya about 1 year ago

  • Tags deleted (qe-yam-refinement)
Actions #10

Updated by JERiveraMoya 11 months ago

  • Status changed from Workable to New
Actions #11

Updated by JERiveraMoya 9 months ago

  • Priority changed from Normal to Low

For ALP the focus will be shifted to Cockpit, so no point to implement this at the moment, needs re-evaluation.

Actions #12

Updated by JERiveraMoya 4 months ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF