From Fedora Project Wiki

(system update important to match release criteria)
(install preupgrade package)
Line 4: Line 4:
# Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 500MB for {{filename|/boot}}).
# Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 500MB for {{filename|/boot}}).
# Do a full system update
# Do a full system update
# Install {{package|preupgrade}}
# Run {{command|preupgrade}} from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization.
# Run {{command|preupgrade}} from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization.
# On the ''Choose desired release'' screen, enable ''unstable test releases''.
# On the ''Choose desired release'' screen, enable ''unstable test releases''.

Revision as of 10:01, 1 November 2011

Description

This case tests upgrading a Fedora system from the current stable release (Fedora 41) to the branched release (Fedora 42) using PreUpgrade.


How to test

  1. Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 500MB for /boot).
  2. Do a full system update
  3. Install preupgrade
  4. Run preupgrade from a command prompt or the Run Application dialog. Provide the requested password for root authorization.
  5. On the Choose desired release screen, enable unstable test releases.
  6. Choose Fedora 42 (Branched) from the list of available upgrade targets, then click Apply.
  7. When the process completes, click Reboot.
  8. The system should reboot, perform the upgrade, and reboot into the new system automatically.
  9. Log in to upgraded system, open a terminal, file browser, or other system applications.

Expected Results

  1. The preupgrade utility will run to completion, without error
  2. The upgrade should complete and reboot without user assistance.
  3. The user is not prompted to address low disk space in /boot
  4. The system should be upgraded to new version without error.
  5. The opened terminal, file browser, or other system applications should display and work correctly.