From Fedora Project Wiki

(create a minimal upgrade test case based on the others)
 
(add the 'associated criterion' block)
Line 1: Line 1:
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Upgrade_requirements}}
{{QA/Test_Case
{{QA/Test_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 a minimal package set.
|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 a minimal package set.

Revision as of 23:06, 25 July 2013

Associated release criterion
This test case is associated with the Fedora_42_MILESTONE_Release_Criteria#CRITERION_NAME 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 (Fedora 41) to the branched release (Fedora 42) using the Fedup CLI with a minimal package set.


How to test

  1. Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 500MB for /boot), selecting the minimal package set.
  2. Do a full system update and reboot
  3. Install the latest version of fedup 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://dl.fedoraproject.org/pub/alt/stage/42_Beta_1.4/Server/(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 42)
    • 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
  5. It must be possible to log in and use yum
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_upgrade_fedup_cli_previous_minimal&oldid=346755"