Template:Testcase upgrade

This template is now obsolete
We have replaced this template with other templates, it's no longer being used. See test list to learn why.

Template documentation [edit]

This documentation is transcluded from Template:Testcase upgrade/doc. It will not be transcluded on pages that use this template.

This template is used to produce multiple upgrade test cases for release validation testing, found at Template:Installation_test_matrix#Upgrade.

Various bits of the content are conditionalized, based on template parameters, to let you produce the test cases that cover upgrading from different configurations.

If the first parameter is set, you'll get a test case for that flavor - e.g. {{Testcase upgrade|server}} to get a test case for upgrading the Server flavor.

If the second parameter is set, you'll get a test case for that package set - e.g. {{Testcase upgrade||minimal}} to get a test case for upgrading the minimal package set.

You should only ever set either the first or the second parameter, don't set both together.

If the third parameter is set to live, the test case will mention a live image; it's only intended to be used with the second parameter set (i.e. a package set - not flavor - test case). e.g. {{Testcase upgrade||KDE|live}} to get a test case which covers upgrading a KDE install either via network install or live image.

If the fourth parameter is set to encrypt, the test case will be for upgrading an encrypted system; e.g. {{Testcase upgrade|workstation|||encrypt}} to get a test case which covers upgrading an encrypted Workstation install.

The fifth parameter can be used to specify the release the test case tests upgrading from. Its value is passed to Template:FedoraVersion as its second parameter, for the two places where that template is used to specify the source release. If not set, the source release will be the current stable release. For e.g. {{Testcase upgrade|||||previous}} will produce a test case for upgrading from the previous stable release. The FedoraVersion documentation explains the values that can be used.

If the sixth parameter is set, the test case will give instructions for upgrading graphically using GNOME Software, and be in the gnome-software package test case category. If it is not set, the test case will give instructions for upgrading using the dnf system-upgrade plugin, and be in the dnf-plugin-system-upgrade package test case category.

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 test case tests upgrading from the current release (presently Fedora 41) to the next release (presently Fedora 42) using the dnf-plugin-system-upgrade CLI.

How to test

1. Perform an installation of Fedora 41 with default partitioning (no less than 500MB for /boot).

1. Install the latest stable version of dnf-plugin-system-upgrade package:

   sudo dnf install --best --refresh dnf-plugin-system-upgrade

2. Download the updates:

   sudo dnf system-upgrade download --refresh --releasever=42

   • You can change 42 to test upgrading to a different Fedora release, of course.
   • If you need to use a local mirror to test a brand new change, you can enable it as normal, i.e. by adding --enablerepo=<name> option to the command line.
3. To aid debugging, run this command to enable a root shell on VT9 during the upgrade boot:

   sudo systemctl add-wants system-update.target debug-shell.service

   If anything goes wrong during upgrade, you can live switch to VT9 and inspect current system state, logs, etc.

4. If downloading has completed without error, run:

   sudo dnf system-upgrade reboot

5. Once the system reboots, the system should boot into the upgrade process and a graphical progress screen should be displayed
   • Pressing Esc should switch from the graphical progress screen to the text progress information display
6. Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu
7. 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. dnf system-upgrade should run to completion, without 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. The upgraded system should meet all relevant Fedora Release Criteria