From Fedora Project Wiki
(attempting to clean up URL formatting a bit, adding tip about updates-testing for installing fedup) |
(fedup is now obsolete, obsolete the tests) |
||
(19 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{admon/ | {{admon/note|Obsolete|As of Fedora 23, fedup has been replaced by the [[DNF_system_upgrade]] plugin. See [[:Category:Upgrade_system]].}} | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This case | |description=This test case tests upgrading from the current release ({{FedoraVersion|long}}) to the branched release ({{FedoraVersion|long|next}}) using the [https://github.com/wgwoods/fedup Fedup] CLI with the default desktop package set. | ||
|actions= | |actions= | ||
# Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 500MB for {{filename|/boot}}), selecting the | # Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 500MB for {{filename|/boot}}), selecting the default package set, or using the default live image. | ||
{{fedup_upgrade_procedure}} | |||
|results= | |results= | ||
{{fedup_upgrade_results}} | |||
# | # Typical desktop applications should display and work correctly | ||
#* Running through the [[Test_Results:Current_Desktop_Test|desktop test cases]] would be good for verification. | |||
#* Running through the [[Test_Results:Current_Desktop_Test|desktop test cases]] would be | |||
}} | }} | ||
[[Category: | [[Category:Obsolete Test Cases]] | ||
Latest revision as of 19:06, 2 November 2015
Description
This test case tests upgrading from the current release (Fedora 41) to the branched release (Fedora 42) using the Fedup CLI with the default desktop package set.
How to test
- Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 500MB for
/boot
), selecting the default package set, or using the default live image. - Do a full system update and reboot
- Install the latest version of
fedup
from the stable or updates repository - 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/rawhide-20241223.n.1/rawhide/(arch)/os - replace (arch) with the correct arch
- Start the upgrade prep by executing:
sudo fedup --network <version> (--instrepo <URL>)
- <version> is the version of Fedora you are upgrading to (currently 42)
- If you are doing pre-release testing, include the --instrepo parameter, with <URL> as the location found in the previous step
- 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
- Check
/var/log/fedup.log
file to see if any errors show up in the output fromfedup
- Reboot the system if
fedup
has completed without error - Once the system reboots, there should be a new entry in the boot menu titled System Upgrade
- Select the System Upgrade option from the boot menu
- 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
- Once the upgrade process has completed, the system should reboot and an option to boot the new release should be on the grub menu
- Log in to the upgraded system, open a terminal, file browser, or other system applications.
Expected Results
fedup
should run to completion, without error- The upgrade process should complete and reboot without user assistance beyond selecting
System Upgrade
from the boot menu - The system should be upgraded to new version without error
- The upgraded system should meet all relevant Fedora Release Criteria
- Typical desktop applications should display and work correctly
- Running through the desktop test cases would be good for verification.