QA:Testcase upgrade gnome-software previous workstation

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#upgrade-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.

Description

This tests upgrading from the previous Workstation release (presently Fedora 40) to the next release (presently Fedora 42) with the Workstation package set or a Live image using the GNOME Software GUI.

Setup

1. Perform an installation of Fedora Workstation 40 with default partitioning.
   • Select the Workstation package set or use the Workstation Live image.
2. Apply all system updates and reboot.

How to test

Upgrade to Rawhide instructions
Skip this box when upgrading to Fedora Branched.

But if you need to perform this test case when testing an upgrade to Rawhide, use the following edits to trick the system into being able to upgrade to it:

1. Navigate to ~/.cache/gnome-software/fedora-pkgdb-collections
2. Run:

   jq '(.collections |= map(if .version == "devel" then .koji_name = "f42" | .status = "Active" | .version = "42" else . end))' fedora.json > fedora_updated.json
   

3. Replace the original file with the updated version:

   mv fedora_updated.json fedora.json

1. Enable showing pre-release Fedora versions using this command:

   gsettings set org.gnome.software show-upgrade-prerelease true

2. Reset gnome-software's counter for showing notifications:

   TIMESTAMP=$(date '+%s' --date='08:00 8 days ago')
   gsettings set org.gnome.software upgrade-notification-timestamp $TIMESTAMP

3. Reboot the system or log out and in again, then wait for a few minutes.
4. A notification of an available upgrade should appear. If it does, click it. If not, note this as a bug, but run gnome-software (Software in the overview), click the Updates button, and click the refresh button at top-left.
5. Check that there is a banner informing you about the new release, with Learn More and Download buttons.
   • If you're trying to perform an N+2 upgrade (i.e. going from Fedora 40 to Fedora 42), the banner should be informing about the N+2 release (Fedora 42), not N+1 (Fedora 41). The same applies to the displayed documentation ("Learn More") and downloaded updates, all of that should be related to N+2 release.
6. Click Learn More, it should load an appropriate document or URL.
   • If it links to an appropriate URL but there is no content for the URL yet, this may be reported to the documentation team, but is not a failure of this test.
7. Click Download. A progress bar should be displayed while the upgrade download takes place.
8. Once the download process completes, click the Install button that should appear.
   • If a dialog asking for administrator authentication appears, complete it.
9. Click the Restart & Install button that should appear next. The system should reboot immediately.
10. Once the system reboots, the system should boot into the upgrade environment and a graphical progress screen should be displayed.
11. Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu.
12. Log in to the upgraded system and test basic system applications (a terminal, file browser, or other, depending on the system flavor).

Expected Results

1. The upgrade tool should run to completion without an error.
2. The upgrade process should complete and reboot without user assistance.
3. The system should be upgraded to the new release without error.
4. If the original system had an encrypted storage, there should be no problem accessing encrypted storage in the upgraded system as well.
5. The upgraded system should meet all relevant Fedora Release Criteria.