From Fedora Project Wiki

(allow setting parameter 3 to 'live' to say 'or live image' for a package set...)
(bah, does the whitespace show up this way?)
Line 3: Line 3:


{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests upgrading from {{FedoraVersion|{{{1|long}}}}} to {{FedoraVersion|{{{1|long}}}|next}}{{#if:{{{2|}}}| with the {{{2}}} package set{{#ifeq:{{{3|}}}|live| or live image|}}|}} using the [https://github.com/wgwoods/fedup Fedup] CLI.
|description=This test case tests upgrading from {{FedoraVersion|{{{1|long}}}}} to {{FedoraVersion|{{{1|long}}}|next}}{{#if:{{{2|}}}|<nowiki> </nowiki>with the {{{2}}} package set{{#ifeq:{{{3|}}}|live| or live image|}}|}} using the [https://github.com/wgwoods/fedup Fedup] CLI.
|actions=
|actions=
# Perform an installation of {{FedoraVersion|{{{1|long}}}}} with default partitioning (no less than 500MB for {{filename|/boot}}){{#if:{{{2|}}}|, selecting the {{{2}}} package set{{#ifeq:{{{3|}}}|live| or using the {{{2}}} live image|}}|}}.
# Perform an installation of {{FedoraVersion|{{{1|long}}}}} with default partitioning (no less than 500MB for {{filename|/boot}}){{#if:{{{2|}}}|, selecting the {{{2}}} package set{{#ifeq:{{{3|}}}|live|<nowiki> </nowiki>or using the {{{2}}} live image|}}|}}.
{{fedup_upgrade_procedure}}
{{fedup_upgrade_procedure}}
|results=
|results=

Revision as of 01:45, 29 January 2015

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.
Note.png
Associated release criterion
This test case is associated with the Fedora_40_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 Fedora 39 to Fedora 40 using the Fedup CLI.


How to test

  1. Perform an installation of Fedora 39 with default partitioning (no less than 500MB for /boot).
  2. Do a full system update and reboot
  3. Install the latest version of Package-x-generic-16.pngfedup from the stable or updates repository
  4. If you are doing pre-release testing, find the installation repository URL for the compose you are testing. If you are testing the current compose, the correct location should be https://kojipkgs.fedoraproject.org/mash/branched-20240328.n.0/40/(arch)/os - replace (arch) with the correct arch
  5. Start the upgrade prep by executing:
    • sudo fedup --network <version> (--instrepo <URL>)
    • <version> is the version of Fedora you are upgrading to (currently 40)
    • If you are doing pre-release testing, include the --instrepo parameter, with <URL> as the location found in the previous step
  6. If you need to use a local mirror to test a brand new change, start the upgrade prep by executing the following command:
    • sudo fedup --network <version> --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL>
    • <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds
  7. Check /var/log/fedup.log file to see if any errors show up in the output from fedup
  8. Reboot the system if fedup has completed without error
  9. Once the system reboots, there should be a new entry in the boot menu titled System Upgrade
  10. Select the System Upgrade option from the boot menu
  11. The system should boot into the upgrade process and a fedup progress screen should be displayed
    • Pressing Esc should switch from the graphical progress screen to the text progress information display
  12. Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu
  13. Log in to the upgraded system, open a terminal, file browser, or other system applications.

Expected Results

  1. fedup should run to completion, without error
  2. The upgrade process should complete and reboot without user assistance beyond selecting System Upgrade from the boot menu
  3. The system should be upgraded to new version without error
  4. The upgraded system should meet all relevant Fedora Release Criteria