Using a new user per feature

uyuni-project · Aug 5, 2022 · 4ebab75 · 4ebab75
1 parent f899fd2
commit 4ebab75
Show file tree

Hide file tree

Showing 142 changed files with 3,457 additions and 4,922 deletions.
diff --git a/testsuite/features/build_validation/init_clients/ceos7_ssh_minion.feature b/testsuite/features/build_validation/init_clients/ceos7_ssh_minion.feature
@@ -1,4 +1,4 @@
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2020-2022 SUSE LLC
 # Licensed under the terms of the MIT license.
 #
 #  1) bootstrap a new CentOS minion via salt-ssh
@@ -10,17 +10,19 @@ Feature: Bootstrap a CentOS 7 Salt SSH minion
   Scenario: Clean up sumaform leftovers on a CentOS 7 Salt SSH minion
     When I perform a full salt minion cleanup on "ceos7_ssh_minion"
 
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
+
   Scenario: Bootstrap a CentOS 7 Salt SSH minion
-    Given I am authorized with the feature's user
-    When I go to the bootstrapping page
+    When I follow the left menu "Systems > Bootstrapping"
     Then I should see a "Bootstrap Minions" text
     When I check "manageWithSSH"
     And I enter the hostname of "ceos7_ssh_minion" as "hostname"
     And I enter "linux" as "password"
     And I select "1-ceos7_ssh_minion_key" from "activationKeys"
-    And I select the hostname of "proxy" from "proxies"
+    And I select the hostname of "proxy" from "proxies" if present
     And I click on "Bootstrap"
-    Then I wait until I see "Successfully bootstrapped host!" text
+    And I wait until I see "Successfully bootstrapped host!" text
     And I wait until onboarding is completed for "ceos7_ssh_minion"
 
 @proxy

diff --git a/testsuite/features/build_validation/init_clients/ceos8_minion.feature b/testsuite/features/build_validation/init_clients/ceos8_minion.feature
@@ -1,4 +1,4 @@
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2020-2022 SUSE LLC
 # Licensed under the terms of the MIT license.
 #
 #  1) bootstrap a new CentOS 8 minion via salt-ssh
@@ -10,16 +10,18 @@ Feature: Bootstrap a CentOS 8 Salt minion
   Scenario: Clean up sumaform leftovers on a CentOS 8 Salt minion
     When I perform a full salt minion cleanup on "ceos8_minion"
 
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
+
   Scenario: Bootstrap a CentOS 8 Salt minion
-    Given I am authorized with the feature's user
-    When I go to the bootstrapping page
+    When I follow the left menu "Systems > Bootstrapping"
     Then I should see a "Bootstrap Minions" text
-    And I enter the hostname of "ceos8_minion" as "hostname"
+    When I enter the hostname of "ceos8_minion" as "hostname"
     And I enter "linux" as "password"
     And I select "1-ceos8_minion_key" from "activationKeys"
-    And I select the hostname of "proxy" from "proxies"
+    And I select the hostname of "proxy" from "proxies" if present
     And I click on "Bootstrap"
-    Then I wait until I see "Successfully bootstrapped host!" text
+    And I wait until I see "Successfully bootstrapped host!" text
     And I wait until onboarding is completed for "ceos8_minion"
 
 @proxy

diff --git a/testsuite/features/build_validation/init_clients/ceos8_ssh_minion.feature b/testsuite/features/build_validation/init_clients/ceos8_ssh_minion.feature
@@ -1,4 +1,4 @@
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2020-2022 SUSE LLC
 # Licensed under the terms of the MIT license.
 #
 #  1) bootstrap a new CentOS minion via salt-ssh
@@ -10,17 +10,19 @@ Feature: Bootstrap a CentOS 8 Salt SSH minion
   Scenario: Clean up sumaform leftovers on a CentOS 8 Salt SSH minion
     When I perform a full salt minion cleanup on "ceos8_ssh_minion"
 
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
+
   Scenario: Bootstrap a CentOS 8 Salt SSH minion
-    Given I am authorized with the feature's user
-    When I go to the bootstrapping page
+    When I follow the left menu "Systems > Bootstrapping"
     Then I should see a "Bootstrap Minions" text
     When I check "manageWithSSH"
     And I enter the hostname of "ceos8_ssh_minion" as "hostname"
     And I enter "linux" as "password"
     And I select "1-ceos8_ssh_minion_key" from "activationKeys"
-    And I select the hostname of "proxy" from "proxies"
+    And I select the hostname of "proxy" from "proxies" if present
     And I click on "Bootstrap"
-    Then I wait until I see "Successfully bootstrapped host!" text
+    And I wait until I see "Successfully bootstrapped host!" text
     And I wait until onboarding is completed for "ceos8_ssh_minion"
 
 @proxy

diff --git a/testsuite/features/build_validation/init_clients/sle12sp4_client.feature b/testsuite/features/build_validation/init_clients/sle12sp4_client.feature
@@ -1,4 +1,4 @@
-# Copyright (c) 2015 SUSE LLC
+# Copyright (c) 2015-2021 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @sle12sp4_client
@@ -9,13 +9,15 @@ Feature: Bootstrap a SLES 12 SP4 traditional client
 
   Scenario: Register a SLES 12 SP4 traditional client
     When I bootstrap traditional client "sle12sp4_client" using bootstrap script with activation key "1-sle12sp4_client_key" from the proxy
-    And I install package "spacewalk-client-setup spacewalk-oscap mgr-cfg-actions" on this "sle12sp4_client"
+    And I install package "spacewalk-client-setup mgr-cfg-actions" on this "sle12sp4_client"
     And I run "mgr-actions-control --enable-all" on "sle12sp4_client"
     Then I should see "sle12sp4_client" via spacecmd
 
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
+
   Scenario: The onboarding of SLES 12 SP4 traditional client is completed
-    Given I am authorized with the feature's user
-    Then I wait until onboarding is completed for "sle12sp4_client"
+    When I wait until onboarding is completed for "sle12sp4_client"
 
   Scenario: Check registration values of SLES 12 SP4 traditional client
     Given I update the profile of "sle12sp4_client"
@@ -42,10 +44,3 @@ Feature: Bootstrap a SLES 12 SP4 traditional client
     When I follow "Details" in the content area
     And I follow "Proxy" in the content area
     Then I should see "sle12sp4_client" hostname
-
-  Scenario: Check tab links "Software" => "Patches" of sle12sp4 traditional
-    Given I am on the Systems overview page of this "sle12sp4_client"
-    When I follow "Software" in the content area
-    And I follow "Patches" in the content area
-    Then I should see a "Relevant Patches" text
-    And I should see a "Show" button
diff --git a/testsuite/features/build_validation/init_clients/sle12sp4_minion.feature b/testsuite/features/build_validation/init_clients/sle12sp4_minion.feature
@@ -1,61 +1,47 @@
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2020-2022 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @sle12sp4_minion
-Feature: Be able to bootstrap a sle12sp4 Salt minion via the GUI
+Feature: Bootstrap a SLES 12 SP4 Salt minion
 
   Scenario: Clean up sumaform leftovers on a SLES 12 SP4 Salt minion
     When I perform a full salt minion cleanup on "sle12sp4_minion"
 
-  Scenario: Create the bootstrap repository for a Salt client
-    Given I am authorized with the feature's user
-    And I create the "x86_64" bootstrap repository for "sle12sp4_minion" on the server
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
 
-  Scenario: Bootstrap a sle12sp4 minion
-    Given I am authorized with the feature's user
-    When I go to the bootstrapping page
+  Scenario: Bootstrap a SLES 12 SP4 minion
+    When I follow the left menu "Systems > Bootstrapping"
     Then I should see a "Bootstrap Minions" text
     When I enter the hostname of "sle12sp4_minion" as "hostname"
     And I enter "22" as "port"
     And I enter "root" as "user"
     And I enter "linux" as "password"
     And I select "1-sle12sp4_minion_key" from "activationKeys"
-    And I select the hostname of "proxy" from "proxies"
+    And I select the hostname of "proxy" from "proxies" if present
     And I click on "Bootstrap"
     And I wait until I see "Successfully bootstrapped host!" text
     And I wait until onboarding is completed for "sle12sp4_minion"
 
-  Scenario: Check the new bootstrapped sle12sp4 minion in System Overview page
-    Given I am authorized with the feature's user
-    And I go to the minion onboarding page
+  Scenario: Check the new bootstrapped SLES 12 SP4 minion in System Overview page
+    When I follow the left menu "Salt > Keys"
     Then I should see a "accepted" text
     And the Salt master can reach "sle12sp4_minion"
 
 @proxy
-  Scenario: Check connection from sle12sp4 minion to proxy
+  Scenario: Check connection from SLES 12 SP4 minion to proxy
     Given I am on the Systems overview page of this "sle12sp4_minion"
     When I follow "Details" in the content area
     And I follow "Connection" in the content area
     Then I should see "proxy" short hostname
 
 @proxy
-  Scenario: Check registration on proxy of sle12sp4 minion
+  Scenario: Check registration on proxy of SLES 12 SP4 minion
     Given I am on the Systems overview page of this "proxy"
     When I follow "Details" in the content area
     And I follow "Proxy" in the content area
     Then I should see "sle12sp4_minion" hostname
 
-  # bsc#1085436 - Apache returns 403 Forbidden after a zypper refresh on minion
-  Scenario: Check the new channel is working
-    When I refresh the metadata for "sle12sp4_minion"
-
-  Scenario: Detect latest Salt changes on the sle12sp4 minion
-    When I query latest Salt changes on "sle12sp4_minion"
-
-  Scenario: Check spacecmd system ID of bootstrapped sle12sp4 minion
-    Given I am on the Systems overview page of this "sle12sp4_minion"
-    Then I run spacecmd listevents for "sle12sp4_minion"
-
-  Scenario: Check events history for failures on sle12sp4 minion
+  Scenario: Check events history for failures on SLES 12 SP4 minion
     Given I am on the Systems overview page of this "sle12sp4_minion"
     Then I check for failed events on history event page
diff --git a/testsuite/features/build_validation/init_clients/sle15_client.feature b/testsuite/features/build_validation/init_clients/sle15_client.feature
@@ -1,4 +1,4 @@
-# Copyright (c) 2015 SUSE LLC
+# Copyright (c) 2015-2021 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @sle15_client
@@ -9,13 +9,15 @@ Feature: Bootstrap a SLES 15 traditional client
 
   Scenario: Register a SLES 15 traditional client
     When I bootstrap traditional client "sle15_client" using bootstrap script with activation key "1-sle15_client_key" from the proxy
-    And I install package "spacewalk-client-setup spacewalk-oscap mgr-cfg-actions" on this "sle15_client"
+    And I install package "spacewalk-client-setup mgr-cfg-actions" on this "sle15_client"
     And I run "mgr-actions-control --enable-all" on "sle15_client"
     Then I should see "sle15_client" via spacecmd
 
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
+
   Scenario: The onboarding of SLES 15 traditional client is completed
-    Given I am authorized with the feature's user
-    Then I wait until onboarding is completed for "sle15_client"
+    When I wait until onboarding is completed for "sle15_client"
 
   Scenario: Check registration values of SLES 15 traditional client
     Given I update the profile of "sle15_client"
@@ -42,10 +44,3 @@ Feature: Bootstrap a SLES 15 traditional client
     When I follow "Details" in the content area
     And I follow "Proxy" in the content area
     Then I should see "sle15_client" hostname
-
-  Scenario: Check tab links "Software" => "Patches" of SLES 15 traditional
-    Given I am on the Systems overview page of this "sle15_client"
-    When I follow "Software" in the content area
-    And I follow "Patches" in the content area
-    Then I should see a "Relevant Patches" text
-    And I should see a "Show" button
diff --git a/testsuite/features/build_validation/init_clients/sle15_minion.feature b/testsuite/features/build_validation/init_clients/sle15_minion.feature
@@ -1,33 +1,30 @@
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2020-2022 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @sle15_minion
-Feature: Be able to bootstrap a SLES 15 Salt minion
+Feature: Bootstrap a SLES 15 Salt minion
 
   Scenario: Clean up sumaform leftovers on a SLES 15 Salt minion
     When I perform a full salt minion cleanup on "sle15_minion"
 
-  Scenario: Create the bootstrap repository for a Salt client
-    Given I am authorized with the feature's user
-    And I create the "x86_64" bootstrap repository for "sle15_minion" on the server
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
 
   Scenario: Bootstrap a SLES 15 minion
-    Given I am authorized with the feature's user
-    When I go to the bootstrapping page
+    When I follow the left menu "Systems > Bootstrapping"
     Then I should see a "Bootstrap Minions" text
     When I enter the hostname of "sle15_minion" as "hostname"
     And I enter "22" as "port"
     And I enter "root" as "user"
     And I enter "linux" as "password"
     And I select "1-sle15_minion_key" from "activationKeys"
-    And I select the hostname of "proxy" from "proxies"
+    And I select the hostname of "proxy" from "proxies" if present
     And I click on "Bootstrap"
     And I wait until I see "Successfully bootstrapped host!" text
     And I wait until onboarding is completed for "sle15_minion"
 
   Scenario: Check the new bootstrapped SLES 15 minion in System Overview page
-    Given I am authorized with the feature's user
-    And I go to the minion onboarding page
+    When I follow the left menu "Salt > Keys"
     Then I should see a "accepted" text
     And the Salt master can reach "sle15_minion"
 
@@ -45,30 +42,6 @@ Feature: Be able to bootstrap a SLES 15 Salt minion
     And I follow "Proxy" in the content area
     Then I should see "sle15_minion" hostname
 
-  # bsc#1085436 - Apache returns 403 Forbidden after a zypper refresh on minion
-  Scenario: Check the new channel for SLES 15 minion is working
-    When I refresh the metadata for "sle15_minion"
-
-  Scenario: Detect latest Salt changes on the SLES 15 minion
-    When I query latest Salt changes on "sle15_minion"
-
-  Scenario: Run a remote command on normal SLES 15 minion
-    Given I am authorized as "testing" with password "testing"
-    When I follow the left menu "Salt > Remote Commands"
-    Then I should see a "Remote Commands" text in the content area
-    When I enter command "file /tmp"
-    And I click on preview
-    Then I should see "sle15_minion" hostname
-    And I wait until I do not see "pending" text
-    When I click on run
-    And I wait until I do not see "pending" text
-    And I expand the results for "sle15_minion"
-    Then I should see "/tmp: sticky, directory" in the command output for "sle15_minion"
-
-  Scenario: Check spacecmd system ID of bootstrapped SLES 15 minion
-    Given I am on the Systems overview page of this "sle15_minion"
-    Then I run spacecmd listevents for "sle15_minion"
-
   Scenario: Check events history for failures on SLES 15 minion
     Given I am on the Systems overview page of this "sle15_minion"
     Then I check for failed events on history event page
diff --git a/testsuite/features/build_validation/init_clients/sle15sp1_client.feature b/testsuite/features/build_validation/init_clients/sle15sp1_client.feature
@@ -1,4 +1,4 @@
-# Copyright (c) 2015 SUSE LLC
+# Copyright (c) 2020-2021 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @sle15sp1_client
@@ -9,13 +9,15 @@ Feature: Bootstrap a SLES 15 SP1 traditional client
 
   Scenario: Register a SLES 15 SP1 traditional client
     When I bootstrap traditional client "sle15sp1_client" using bootstrap script with activation key "1-sle15sp1_client_key" from the proxy
-    And I install package "spacewalk-client-setup spacewalk-oscap mgr-cfg-actions" on this "sle15sp1_client"
+    And I install package "spacewalk-client-setup mgr-cfg-actions" on this "sle15sp1_client"
     And I run "mgr-actions-control --enable-all" on "sle15sp1_client"
     Then I should see "sle15sp1_client" via spacecmd
 
+  Scenario: Log in as admin user
+    Given I am authorized for the "Admin" section
+
   Scenario: The onboarding of SLES 15 SP1 traditional client is completed
-    Given I am authorized with the feature's user
-    Then I wait until onboarding is completed for "sle15sp1_client"
+    When I wait until onboarding is completed for "sle15sp1_client"
 
   Scenario: Check registration values of SLES 15 SP1 traditional
     Given I update the profile of "sle15sp1_client"
@@ -42,10 +44,3 @@ Feature: Bootstrap a SLES 15 SP1 traditional client
     When I follow "Details" in the content area
     And I follow "Proxy" in the content area
     Then I should see "sle15sp1_client" hostname
-
-  Scenario: Check tab links "Software" => "Patches" for SLES 15 SP1 traditional
-    Given I am on the Systems overview page of this "sle15sp1_client"
-    When I follow "Software" in the content area
-    And I follow "Patches" in the content area
-    Then I should see a "Relevant Patches" text
-    And I should see a "Show" button