Project

General

Profile

action #122779

Updated by JERiveraMoya over 1 year ago

#### Motivation 
 This module could be used to enable ALP Build Repository: 
 https://documentation.suse.com/alp/all/single-html/alp/#how-it-works-transactional-update-repositories 

 The sequence of steps in the test could go like this: 
 1. Open `yast2 repositories` in container (see additional information) Navigate to Software/Software Repositories 
 2. Select explicitly table row 'ALP Build Repository' not relying in the order displayed: 
    example: `curl -X POST 'http://<ip>:<port>/v1/widgets?id=table&action=select&value=ALP+Build+Repository&column=Name&row=0'` 
  
 3. Enable ALP Build Repository 
 4. Refresh All repositories enabled 
 5. Press OK 
 6. 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 -E | grep 'ALP Build Repository'` 

 (on-going) 

 #### Scope 
 All architectures. 
 Job group: https://openqa.opensuse.org/tests/overview?distri=alp&version=0.1&build=20221216&groupid=100 
 Staging: https://openqa.opensuse.org/group_overview/105 

 #### Acceptance criteria 
 AC1: Automate with libyui-rest-api using POM (using directly Pages in the test, without Controllers) 
 AC2: Implemente One Page Object as appear to user as only one page POM should have 4 pages, including the navigation at the bottom 
 AC3: Focus on readability of the test (no comments required in general) 

 #### Additional information 
 Enable it in test suite created in #122218 
 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 of the repos (basically read the screen) but things might change too much to do that now.

Back