Using a new user per feature, to facilitate parallelization of second…

…ary_parallelizable.yml in CI (#5743)

* Using a new user per feature

* Removing refactors made to enable parallel tests, moved to this branch qe-refactor-enabling-parallel-tests

* Updating the Copyright year

testsuite/features/secondary/allcli_config_channel.feature

@@ -1,11 +1,11 @@
-# Copyright (c) 2018-2022 SUSE LLC
+# Copyright (c) 2018-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @scope_configuration_channels
 Feature: Management of configuration of all types of clients in a single channel
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Create a configuration channel for mixed client types
     When I follow the left menu "Configuration > Channels"
@@ -164,7 +164,7 @@ Feature: Management of configuration of all types of clients in a single channel
     And I click on "Compare Files"
     And I click on "Schedule Compare"
     Then I should see a "1 files scheduled for comparison." text
-    When I wait until event "Show differences between profiled config files and deployed config files scheduled by admin" is completed
+    When I wait until event "Show differences between profiled config files and deployed config files scheduled" is completed
     Then I should see a "Differences exist" link
     When I follow "Differences exist"
     Then I should see a "+COLOR=white" text

testsuite/features/secondary/allcli_overview_systems_details.feature

@@ -1,18 +1,19 @@
-# Copyright (c) 2017-2022 SUSE LLC.
+# Copyright (c) 2017-2024 SUSE LLC.
 # Licensed under the terms of the MIT license.
 
 @scope_visualization
 Feature: The system details of each minion and client provides an overview of the system
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
+
 @sle_minion
   Scenario: SLE minion hardware refresh
     Given I navigate to the Systems overview page of this "sle_minion"
     When I follow "Hardware"
     And I click on "Schedule Hardware Refresh"
     Then I should see a "You have successfully scheduled a hardware profile refresh" text
-    When I wait until event "Hardware List Refresh scheduled by admin" is completed
+    When I wait until event "Hardware List Refresh scheduled" is completed
     And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion"
 
 @sle_minion
@@ -34,7 +35,7 @@ Feature: The system details of each minion and client provides an overview of th
     When I follow "Hardware"
     And I click on "Schedule Hardware Refresh"
     Then I should see a "You have successfully scheduled a hardware profile refresh" text
-    When I wait until event "Hardware List Refresh scheduled by admin" is completed
+    When I wait until event "Hardware List Refresh scheduled" is completed
     And I wait until there is no Salt job calling the module "hardware.profileupdate" on "rhlike_minion"
 
 @rhlike_minion
@@ -56,7 +57,7 @@ Feature: The system details of each minion and client provides an overview of th
     When I follow "Hardware"
     And I click on "Schedule Hardware Refresh"
     Then I should see a "You have successfully scheduled a hardware profile refresh" text
-    When I wait until event "Hardware List Refresh scheduled by admin" is completed
+    When I wait until event "Hardware List Refresh scheduled" is completed
     And I wait until there is no Salt job calling the module "hardware.profileupdate" on "deblike_minion"
 
 @deblike_minion
@@ -78,7 +79,7 @@ Feature: The system details of each minion and client provides an overview of th
     When I follow "Hardware"
     And I click on "Schedule Hardware Refresh"
     Then I should see a "You have successfully scheduled a hardware profile refresh" text
-    And I wait until event "Hardware List Refresh scheduled by admin" is completed
+    And I wait until event "Hardware List Refresh scheduled" is completed
 
   @ssh_minion
   Scenario: SSH-managed minion grains are displayed correctly on the details page

testsuite/features/secondary/allcli_reboot.feature

@@ -1,4 +1,4 @@
-# Copyright (c) 2017-2022 SUSE LLC.
+# Copyright (c) 2017-2024 SUSE LLC.
 # Licensed under the terms of the MIT license.
 #
 # Idempotency note:
@@ -14,16 +14,16 @@
 # - features/secondary/min_deblike_openscap_audit.feature
 # - features/secondary/min_deblike_remote_command.feature
 # - features/secondary/min_deblike_ssh.feature
-# If the minions take over the alloted 10 minutes to reboot, 
+# If the minions take over the alloted 10 minutes to reboot,
 # the following features could fail due to the minions not being reachable.
 # Depending on how long they take to reboot, even more features could fail.
 
 @skip_if_github_validation
 @scope_onboarding
 Feature: Reboot systems managed by Uyuni
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
 @ssh_minion
   Scenario: Reboot the SSH-managed SLES minion
@@ -41,7 +41,7 @@ Feature: Reboot systems managed by Uyuni
     And I should see a "Reboot system" button
     And I click on "Reboot system"
     Then I should see a "Reboot scheduled for system" text
-    When I wait at most 600 seconds until event "System reboot scheduled by admin" is completed
+    When I wait at most 600 seconds until event "System reboot scheduled" is completed
     And I should see a "Reboot completed." text
 
 @rhlike_minion
@@ -52,7 +52,7 @@ Feature: Reboot systems managed by Uyuni
     And I should see a "Reboot system" button
     When I click on "Reboot system"
     Then I should see a "Reboot scheduled for system" text
-    When I wait at most 600 seconds until event "System reboot scheduled by admin" is completed
+    When I wait at most 600 seconds until event "System reboot scheduled" is completed
     Then I should see a "Reboot completed." text
 
 @deblike_minion
@@ -63,5 +63,5 @@ Feature: Reboot systems managed by Uyuni
     And I should see a "Reboot system" button
     When I click on "Reboot system"
     Then I should see a "Reboot scheduled for system" text
-    When I wait at most 600 seconds until event "System reboot scheduled by admin" is completed
+    When I wait at most 600 seconds until event "System reboot scheduled" is completed
     Then I should see a "Reboot completed." text

testsuite/features/secondary/allcli_software_channels.feature

@@ -5,8 +5,8 @@
 @scc_credentials
 Feature: Channel subscription via SSM
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
 @sle_minion
 @susemanager
@@ -102,7 +102,7 @@ Feature: Channel subscription via SSM
 @sle_minion
   Scenario: Check channel change has completed for the SLES minion
     Given I am on the Systems overview page of this "sle_minion"
-    When I wait until event "Subscribe channels scheduled by admin" is completed
+    When I wait until event "Subscribe channels scheduled" is completed
     Then I should see "The client completed this action on" at least 3 minutes after I scheduled an action
 
 @sle_minion

testsuite/features/secondary/allcli_software_channels_dependencies.feature

@@ -1,12 +1,12 @@
-# Copyright (c) 2018-2023 SUSE LLC
+# Copyright (c) 2018-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @scope_changing_software_channels
 @scc_credentials
 Feature: Channel subscription with recommended or required dependencies
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Pre-requisite: remove remaining systems from SSM after software channel tests
     When I click on the clear SSM button

testsuite/features/secondary/allcli_system_group.feature

@@ -1,12 +1,12 @@
-# Copyright (c) 2017-2022 SUSE LLC
+# Copyright (c) 2017-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @skip_if_github_validation
 @scope_visualization
 Feature: Manage a group of systems
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Fail to create a group with only its name
     When I follow the left menu "Systems > System Groups"
@@ -62,7 +62,7 @@ Feature: Manage a group of systems
     And I should see "sle_minion" as link
 
    #container already has locale formula installed
-   @skip_if_containerized_server 
+   @skip_if_containerized_server
    Scenario: Install the locale formula package on the server
      When I manually install the "locale" formula on the server
 
@@ -106,7 +106,7 @@ Feature: Manage a group of systems
 
   # Red Hat-like minion is intentionally not removed from group
 
-  @skip_if_containerized_server 
+  @skip_if_containerized_server
   Scenario: Cleanup: uninstall formula from the server
     When I manually uninstall the "locale" formula from the server
 

testsuite/features/secondary/buildhost_docker_build_image.feature

@@ -1,11 +1,11 @@
-# Copyright (c) 2017-2023 SUSE LLC
+# Copyright (c) 2017-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 #
 # Basic images do not contain zypper nor the name of the server,
 # so the inspect functionality is not tested here.
 #
 # This feature is a dependency for:
-# - features/secondary/srv_docker_cve_audit.feature 
+# - features/secondary/srv_docker_cve_audit.feature
 #
 # This feature depends on:
 # - features/secondary/min_docker_api.feature
@@ -19,8 +19,8 @@
 @no_auth_registry
 Feature: Build container images
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Create a simple image profile without activation key
     When I follow the left menu "Images > Profiles"
@@ -59,7 +59,7 @@ Feature: Build container images
   Scenario: Build the suse_key image with and without activation key
     Given I am on the Systems overview page of this "build_host"
     When I schedule the build of image "suse_key" via API calls
-    And I wait at most 660 seconds until event "Image Build suse_key scheduled by admin" is completed
+    And I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed
     # We should see the same result via API.
     # Also, check that all inspect actions are finished:
     And I wait at most 600 seconds until image "suse_key" with version "latest" is built successfully via API
@@ -70,15 +70,15 @@ Feature: Build container images
   Scenario: Build the suse_simple image with and without activation key
     Given I am on the Systems overview page of this "build_host"
     When I schedule the build of image "suse_simple" via API calls
-    And I wait at most 660 seconds until event "Image Build suse_simple scheduled by admin" is completed
+    And I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed
     And I wait at most 600 seconds until image "suse_simple" with version "latest" is built successfully via API
     And I wait at most 300 seconds until image "suse_simple" with version "latest" is inspected successfully via API
     Then the list of packages of image "suse_simple" with version "latest" is not empty
 
   Scenario: Build the suse_real_key image with and without activation key
-    Given I am on the Systems overview page of this "build_host"  
+    Given I am on the Systems overview page of this "build_host"
     When I schedule the build of image "suse_real_key" via API calls
-    And I wait at most 660 seconds until event "Image Build suse_real_key scheduled by admin" is completed
+    And I wait at most 660 seconds until event "Image Build suse_real_key scheduled" is completed
     And I wait at most 60 seconds until all "3" container images are built correctly on the Image List page
     And I wait at most 600 seconds until image "suse_real_key" with version "latest" is built successfully via API
     And I wait at most 300 seconds until image "suse_real_key" with version "latest" is inspected successfully via API

testsuite/features/secondary/buildhost_osimage_build_image.feature

@@ -1,4 +1,4 @@
-# Copyright (c) 2018-2023 SUSE LLC
+# Copyright (c) 2018-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 #
 # This feature relies on having properly configured
@@ -22,8 +22,10 @@
 @scope_building_container_images
 Feature: Build OS images
 
+  Scenario: Log in as org admin user
+    Given I am authorized
+
   Scenario: Create an OS image profile with activation key
-    Given I am authorized for the "Admin" section
     When I follow the left menu "Images > Profiles"
     And I follow "Create"
     And I enter "suse_os_image" as "label"

testsuite/features/secondary/min_activationkey.feature

@@ -9,8 +9,8 @@
 @scope_onboarding
 Feature: Bootstrap a Salt minion via the GUI with an activation key
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Delete SLES minion system profile
     Given I am on the Systems overview page of this "sle_minion"

testsuite/features/secondary/min_ansible_control_node.feature

@@ -1,12 +1,12 @@
-# Copyright (c) 2021-2023 SUSE LLC
+# Copyright (c) 2021-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @skip_if_github_validation
 @scope_ansible
 Feature: Operate an Ansible control node in a normal minion
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Pre-requisite: Deploy test playbooks and inventory file
     When I deploy testing playbooks and inventory files to "sle_minion"
@@ -33,7 +33,7 @@ Feature: Operate an Ansible control node in a normal minion
     Given I am on the Systems overview page of this "sle_minion"
     When I follow "States" in the content area
     And I click on "Apply Highstate"
-    And I wait until event "Apply highstate scheduled by admin" is completed
+    And I wait until event "Apply highstate scheduled" is completed
     Then "ansible" should be installed on "sle_minion"
 
   Scenario: The Ansible tab appears in the system overview page
@@ -78,7 +78,7 @@ Feature: Operate an Ansible control node in a normal minion
     And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select"
     And I click on "Schedule"
     Then I should see a "Playbook execution has been scheduled" text
-    And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled by admin" is completed
+    And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed
     And file "/tmp/file.txt" should exist on "sle_minion"
 
   Scenario: Cleanup: Disable Ansible and remove test playbooks and inventory file
@@ -100,4 +100,4 @@ Feature: Operate an Ansible control node in a normal minion
   Scenario: Cleanup: Disable client tools repositories
     Given I am on the Systems overview page of this "sle_minion"
     When I disable the repositories "tools_pool_repo os_pool_repo" on this "sle_minion"
-    And I refresh the metadata for "sle_minion"
+    And I refresh the metadata for "sle_minion"

testsuite/features/secondary/min_bootstrap_api.feature

@@ -9,8 +9,8 @@
 @scope_onboarding
 Feature: Register a Salt minion via API
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Delete SLES minion system profile before API bootstrap test
     Given I am on the Systems overview page of this "sle_minion"
@@ -62,7 +62,7 @@ Feature: Register a Salt minion via API
     Then I should see a "Confirm Software Channel Change" text
     When I click on "Confirm"
     Then I should see a "Changing the channels has been scheduled." text
-    And I wait until event "Subscribe channels scheduled by admin" is completed
+    And I wait until event "Subscribe channels scheduled" is completed
 
 @uyuni
   Scenario: API bootstrap: subscribe to base channel
@@ -83,7 +83,7 @@ Feature: Register a Salt minion via API
     Then I should see a "Confirm Software Channel Change" text
     When I click on "Confirm"
     Then I should see a "Changing the channels has been scheduled." text
-    And I wait until event "Subscribe channels scheduled by admin" is completed
+    And I wait until event "Subscribe channels scheduled" is completed
 
   Scenario: Check events history for failures on SLES minion after API bootstrap
     Given I am on the Systems overview page of this "sle_minion"

testsuite/features/secondary/min_bootstrap_negative.feature

@@ -1,4 +1,4 @@
-# Copyright (c) 2021-2022 SUSE LLC
+# Copyright (c) 2021-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @skip_if_github_validation
@@ -9,8 +9,8 @@ Feature: Negative tests for bootstrapping normal minions
   As an authorized user
   I want to avoid registration with invalid input parameters
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Bootstrap should fail when minion already exists
     When I follow the left menu "Systems > Bootstrapping"

testsuite/features/secondary/min_bootstrap_reactivation.feature

@@ -1,4 +1,4 @@
-# Copyright (c) 2021-2023 SUSE LLC
+# Copyright (c) 2021-2024 SUSE LLC
 # Licensed under the terms of the MIT license.
 
 @skip_if_github_validation
@@ -9,8 +9,8 @@ Feature: Bootstrapping with reactivation key
   As an authorized user
   I want to avoid re-registration with invalid input parameters
 
-  Scenario: Log in as admin user
-    Given I am authorized for the "Admin" section
+  Scenario: Log in as org admin user
+    Given I am authorized
 
   Scenario: Generate a re-activation key
     Given I am on the Systems overview page of this "sle_minion"
@@ -63,7 +63,7 @@ Feature: Bootstrapping with reactivation key
     When I follow "Events" in the content area
     And I follow "History" in the content area
     And I wait until I see "Server reactivated as Salt minion" text, refreshing the page
-    And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled by admin" is completed
+    And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed
 
   Scenario: Cleanup: delete SLES minion after reactivation tests
     Given I am on the Systems overview page of this "sle_minion"