QE: fix checks on dummy RPM packages

testsuite/features/secondary/min_check_patches_install.feature

@@ -42,7 +42,7 @@ Feature: Display patches
     And I follow "andromeda-dummy-6789"
     And I follow "Packages"
     Then I should see a "Fake-RPM-SUSE-Channel" link
-    And I should see a "sha512:6bc584eb0af1bc04705c78e59ca0e4154ea86c46cd75abee57c82bfc4ebb57f3660ed21e9aceceae03855264e163853acbcde88005609d773c20f185587f70cc" text
+    And I should see a "sha512:83601d7345101d0fce603c9e920ab9868f1499ae38c2e62951a6082ec0737af29c2acb9f643f8f28eee27bb731dad33a431593042ce32165b03489909f4fac10" text
     And I should see a "andromeda-dummy-2.0-1.1-noarch" link
 
   Scenario: Check relevant patches for this client

testsuite/features/secondary/min_rhlike_salt_install_package_and_patch.feature

@@ -53,7 +53,7 @@ Feature: Install a patch on the Red Hat-like minion via Salt through the UI
     And I click on "Apply Patches"
     And I click on "Confirm"
     Then I should see a "1 patch update has been scheduled for" text
-    And I wait for "virgo-dummy-2.0-1.1" to be installed on "rhlike_minion"
+    And I wait for "virgo-dummy-2.0-1.2" to be installed on "rhlike_minion"
 
   Scenario: Install a package on the Red Hat-like minion
     When I follow "Software" in the content area

testsuite/features/secondary/min_salt_install_package.feature

@@ -39,7 +39,7 @@ Feature: Install a patch on the client via Salt through the UI
     And I click on "Apply Patches"
     And I click on "Confirm"
     Then I should see a "1 patch update has been scheduled for" text
-    And I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion"
+    And I wait for "virgo-dummy-2.0-1.2" to be installed on "sle_minion"
     And vendor change should be enabled for package actions on "sle_minion"
 
   Scenario: Cleanup: remove virgo-dummy package from SLE minion

testsuite/features/secondary/min_salt_install_with_staging.feature

@@ -49,15 +49,15 @@ Feature: Install a package on the SLES minion with staging enabled
     And I follow "Software" in the content area
     And I follow "Packages" in the content area
     And I follow "Install" in the content area
-    And I enter "orion-dummy-1.1-1.1" as the filtered package name
+    And I enter "orion-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion"
+    When I check row with "orion-dummy-1.1-1.2" and arch of "sle_minion"
     And I click on "Install Selected Packages"
     And I pick 3 minutes from now as schedule time
     And I click on "Confirm"
     Then I should see a "1 package install has been scheduled for" text
-    And I wait until the package "orion-dummy-1.1-1.1" has been cached on this "sle_minion"
-    And I wait for "orion-dummy-1.1-1.1" to be installed on "sle_minion"
+    And I wait until the package "orion-dummy-1.1-1.2" has been cached on this "sle_minion"
+    And I wait for "orion-dummy-1.1-1.2" to be installed on "sle_minion"
 
   Scenario: Install patch in the future and check for staging
     And I follow "Software" in the content area

testsuite/features/secondary/min_salt_lock_packages.feature

@@ -3,7 +3,7 @@
 #
 # This feature can cause failures in the following features:
 # - features/secondary/min_salt_install_with_staging.feature
-# If the "orion-dummy-1.1-1.1" is not properly unlocked
+# If the "orion-dummy-1.1-1.2" is not properly unlocked
 
 @sle_minion
 @scope_salt
@@ -21,64 +21,64 @@ Feature: Lock packages on SLES salt minion
     Given I am on the Systems overview page of this "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion"
+    And I check row with "hoag-dummy-1.1-1.2" and arch of "sle_minion"
     And I click on "Lock"
     Then I should see a "Packages has been requested for being locked." text
     When I wait until event "Lock packages scheduled" is completed
-    Then "hoag-dummy-1.1-1.1" is locked on "sle_minion"
+    Then "hoag-dummy-1.1-1.2" is locked on "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    Then package "hoag-dummy-1.1-1.1" is reported as locked
+    Then package "hoag-dummy-1.1-1.2" is reported as locked
 
   Scenario: Attempt to install a locked package on the client
     Given I am on the Systems overview page of this "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And package "hoag-dummy-1.1-1.1" is reported as locked
+    And package "hoag-dummy-1.1-1.2" is reported as locked
     And I follow "Install"
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion"
+    And I check row with "hoag-dummy-1.1-1.2" and arch of "sle_minion"
     And I click on "Install Selected Packages"
     And I click on "Confirm"
     Then I should see a "1 package install has been scheduled for" text
     When I follow "Events"
     And I follow "History"
     And I wait until I see the event "Package Install/Upgrade scheduled" completed during last minute, refreshing the page
     And I follow the event "Package Install/Upgrade scheduled" completed during last minute
-    Then the package scheduled is "hoag-dummy-1.1-1.1"
+    Then the package scheduled is "hoag-dummy-1.1-1.2"
     And the action status is "Failed"
 
   Scenario: Unlock a package on the client
     Given I am on the Systems overview page of this "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And package "hoag-dummy-1.1-1.1" is reported as locked
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And package "hoag-dummy-1.1-1.2" is reported as locked
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion"
+    And I check row with "hoag-dummy-1.1-1.2" and arch of "sle_minion"
     And I click on "Unlock"
     Then I should see a "Packages has been requested for being unlocked." text
     When I wait until event "Lock packages scheduled" is completed
-    Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion"
+    Then "hoag-dummy-1.1-1.2" is unlocked on "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    Then package "hoag-dummy-1.1-1.1" is reported as unlocked
+    Then package "hoag-dummy-1.1-1.2" is reported as unlocked
 
   Scenario: Schedule a package lock
     Given I am on the Systems overview page of this "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion"
+    And I check row with "hoag-dummy-1.1-1.2" and arch of "sle_minion"
     And I click on "Lock"
     Then I should see a "Packages has been requested for being locked." text
-    And package "hoag-dummy-1.1-1.1" is reported as pending to be locked
+    And package "hoag-dummy-1.1-1.2" is reported as pending to be locked
 
   Scenario: Schedule another package lock
     Given I am on the Systems overview page of this "sle_minion"
@@ -91,43 +91,43 @@ Feature: Lock packages on SLES salt minion
     Then I should see a "Packages has been requested for being locked." text
     And package "milkyway-dummy-2.0-1.1" is reported as pending to be locked
     When I wait until event "Lock packages scheduled" is completed
-    Then "hoag-dummy-1.1-1.1" is locked on "sle_minion"
+    Then "hoag-dummy-1.1-1.2" is locked on "sle_minion"
     And "milkyway-dummy-2.0-1.1" is locked on "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    Then package "hoag-dummy-1.1-1.1" is reported as locked
+    Then package "hoag-dummy-1.1-1.2" is reported as locked
     And package "milkyway-dummy-2.0-1.1" is reported as locked
 
   Scenario: Mix package locks and unlock events
     Given I am on the Systems overview page of this "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And package "hoag-dummy-1.1-1.1" is reported as locked
+    And package "hoag-dummy-1.1-1.2" is reported as locked
     And package "milkyway-dummy-2.0-1.1" is reported as locked
-    And I enter "orion-dummy-1.1-1.1" as the filtered package name
+    And I enter "orion-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion"
+    When I check row with "orion-dummy-1.1-1.2" and arch of "sle_minion"
     And I click on "Lock"
     Then I should see a "Packages has been requested for being locked." text
-    And package "orion-dummy-1.1-1.1" is reported as pending to be locked
+    And package "orion-dummy-1.1-1.2" is reported as pending to be locked
     When I follow "Lock / Unlock"
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    And I uncheck row with "hoag-dummy-1.1-1.1" and arch of "sle_minion"
+    And I uncheck row with "hoag-dummy-1.1-1.2" and arch of "sle_minion"
     And I enter "milkyway-dummy-2.0-1.1" as the filtered package name
     And I click on the filter button
     And I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion"
     And I click on "Unlock"
     Then I should see a "Packages has been requested for being unlocked." text
     And package "milkyway-dummy-2.0-1.1" is reported as pending to be unlocked
     When I wait until event "Lock packages scheduled" is completed
-    Then "hoag-dummy-1.1-1.1" is locked on "sle_minion"
+    Then "hoag-dummy-1.1-1.2" is locked on "sle_minion"
     And "milkyway-dummy-2.0-1.1" is unlocked on "sle_minion"
-    And "orion-dummy-1.1-1.1" is locked on "sle_minion"
+    And "orion-dummy-1.1-1.2" is locked on "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    Then package "hoag-dummy-1.1-1.1" is reported as locked
-    And package "orion-dummy-1.1-1.1" is reported as locked
+    Then package "hoag-dummy-1.1-1.2" is reported as locked
+    And package "orion-dummy-1.1-1.2" is reported as locked
     And I enter "milkyway-dummy-2.0-1.1" as the filtered package name
     And I click on the filter button
     And package "milkyway-dummy-2.0-1.1" is reported as unlocked
@@ -139,18 +139,18 @@ Feature: Lock packages on SLES salt minion
     When I click on "Select All"
     And I click on "Unlock"
     Then I should see a "Packages has been requested for being unlocked." text
-    And only packages "hoag-dummy-1.1-1.1, orion-dummy-1.1-1.1" are reported as pending to be unlocked
+    And only packages "hoag-dummy-1.1-1.2, orion-dummy-1.1-1.2" are reported as pending to be unlocked
     When I wait until event "Lock packages scheduled" is completed
-    Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion"
-    And "orion-dummy-1.1-1.1" is unlocked on "sle_minion"
+    Then "hoag-dummy-1.1-1.2" is unlocked on "sle_minion"
+    And "orion-dummy-1.1-1.2" is unlocked on "sle_minion"
     When I follow "Software" in the content area
     And I follow "Lock / Unlock"
-    And I enter "hoag-dummy-1.1-1.1" as the filtered package name
+    And I enter "hoag-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    Then package "hoag-dummy-1.1-1.1" is reported as unlocked
-    And I enter "orion-dummy-1.1-1.1" as the filtered package name
+    Then package "hoag-dummy-1.1-1.2" is reported as unlocked
+    And I enter "orion-dummy-1.1-1.2" as the filtered package name
     And I click on the filter button
-    And package "orion-dummy-1.1-1.1" is reported as unlocked
+    And package "orion-dummy-1.1-1.2" is reported as unlocked
 
   Scenario: Cleanup: remove packages after testing locks
     Then I remove package "orion-dummy" from this "sle_minion"

testsuite/features/secondary/min_salt_software_states.feature

@@ -97,7 +97,7 @@ Feature: Salt package states
     And I click save
     Then I wait until I see "Package states have been saved." text
     And I click apply
-    And I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion"
+    And I wait for "andromeda-dummy-2.0-1.2" to be installed on "sle_minion"
 
   Scenario: Verify the package states
     When I follow "States" in the content area

testsuite/features/secondary/srv_check_channels_page.feature

@@ -36,42 +36,45 @@ Feature: The channels page
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    Then I should see package "andromeda-dummy-2.0-1.1.noarch"
-    And I should see package "hoag-dummy-1.1-1.1.i586"
-    And I should see package "hoag-dummy-1.1-1.1.x86_64"
+    Then I should see package "andromeda-dummy-2.0-1.2.noarch"
+    And I should see package "hoag-dummy-1.1-1.2.i586"
+    And I should see package "hoag-dummy-1.1-1.2.x86_64"
     And I should see package "milkyway-dummy-2.0-1.1.i586"
     And I should see package "milkyway-dummy-2.0-1.1.x86_64"
-    And I should see package "virgo-dummy-2.0-1.1.noarch"
+    # the package may be in the 2nd page of results
+    When I enter "virgo-dummy" as the filtered package name
+    And I click on the filter button
+    Then I should see package "virgo-dummy-2.0-1.2.noarch"
 
   Scenario: Check package metadata
     When I follow the left menu "Software > Channel List > All"
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    And I follow "andromeda-dummy-2.0-1.1.noarch"
+    And I follow "andromeda-dummy-2.0-1.2.noarch"
     Then I should see a "This is the andromeda dummy package used for testing SUSE Manager" text
     And I should see a "Fake-RPM-SUSE-Channel" link
     And I should see a "build.opensuse.org" text
     And I should see a "SHA512sum:" text
-    And I should see a "packages/1/6bc/andromeda-dummy/2.0-1.1/noarch/6bc584eb0af1bc04705c78e59ca0e4154ea86c46cd75abee57c82bfc4ebb57f3660ed21e9aceceae03855264e163853acbcde88005609d773c20f185587f70cc/andromeda-dummy-2.0-1.1.noarch.rpm" text
+    And I should see a "packages/1/1d9/andromeda-dummy/2.0-1.2/noarch/1d9e6629b6b7abc2fe5fee4921523d421139144696302fd701e8434883169b7705db19aef3ddf10a7b68699f6478776a6c4335661e86b5d54880b7be2a661e7c/andromeda-dummy-2.0-1.2.noarch.rpm" text
 
   Scenario: Check package dependencies page
     When I follow the left menu "Software > Channel List > All"
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    And I follow "andromeda-dummy-2.0-1.1.noarch"
+    And I follow "andromeda-dummy-2.0-1.2.noarch"
     And I follow "Dependencies"
     Then I should see a "pam" text
     And I should see a "rpmlib(PayloadIsXz) <= 5.2-1" text
-    And I should see a "andromeda-dummy = 2.0-1.1" text
+    And I should see a "andromeda-dummy = 2.0-1.2" text
 
   Scenario: Check package change log page
     When I follow the left menu "Software > Channel List > All"
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    And I follow "andromeda-dummy-2.0-1.1.noarch"
+    And I follow "andromeda-dummy-2.0-1.2.noarch"
     And I follow "Change Log"
     Then I should see a "[email protected]" text
     And I should see a "version 2.0" text
@@ -81,7 +84,7 @@ Feature: The channels page
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    And I follow "andromeda-dummy-2.0-1.1.noarch"
+    And I follow "andromeda-dummy-2.0-1.2.noarch"
     And I follow "File List"
     Then I should see a "This package contains the following files." text
     And I should see a "/usr/share/doc/packages/andromeda-dummy/COPYING" text

testsuite/features/secondary/srv_check_sync_source_packages.feature

@@ -17,13 +17,16 @@ Feature: Check if source packages were successfully synced
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    And I follow "virgo-dummy-2.0-1.1.noarch"
-    Then I should see a "virgo-dummy-2.0-1.1.src.rpm" text
+    # the package may be in the 2nd page of results
+    And I enter "virgo-dummy" as the filtered package name
+    And I click on the filter button
+    And I follow "virgo-dummy-2.0-1.2.noarch"
+    Then I should see a "virgo-dummy-2.0-1.2.src.rpm" text
 
   Scenario: Check sources for x86_64 package
     When I follow the left menu "Software > Channel List > All"
     And I follow "Show All Child Channels"
     And I follow "Fake-RPM-SUSE-Channel"
     And I follow "Packages"
-    And I follow "blackhole-dummy-1.0-1.1.x86_64"
-    Then I should see a "blackhole-dummy-1.0-1.1.src.rpm" text
+    And I follow "blackhole-dummy-1.0-1.2.x86_64"
+    Then I should see a "blackhole-dummy-1.0-1.2.src.rpm" text

testsuite/features/secondary/srv_clone_channel_npn.feature

@@ -105,8 +105,8 @@ Feature: Clone a channel
     And I follow "Compare"
     And I select "Fake-Clone-3-RPM-SLES15SP4-Channel" from "selected_channel"
     And I click on "View Packages"
-    Then I should see a "andromeda-dummy" text
-    And I should see a "2.0-1.1" link
+    Then I should see a "milkyway-dummy" text
+    And I should see a "2.0-1.2" link
     And I should see a "This channel only" text
 
   Scenario: Cleanup: remove cloned channels