From Fedora Project Wiki
No edit summary |
(obsolete this) |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{admon/important|This test case is obsolete|PreUpgrade has been replaced by FedUp.}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This case tests upgrading a Fedora system from the previous stable release ({{FedoraVersion|long|previous}}) to the | |description=This case tests upgrading a Fedora system from the previous stable release ({{FedoraVersion|long|previous}}) to the branched release ({{FedoraVersion|long|next}}) using [[PreUpgrade]]. | ||
|actions= | |actions= | ||
# Perform an installation of the | # Perform an installation of the stable release (e.g. {{FedoraVersion|long|previous}}) with default partitioning (500MB for {{filename|/boot}}). | ||
# Install | # 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''. | ||
# Choose '' | # Choose ''{{FedoraVersion|long|next}} (Branched)'' from the list of available upgrade targets, then click ''Apply''. | ||
# When the process completes, click ''Reboot''. | # When the process completes, click ''Reboot''. | ||
# The system should reboot, perform the upgrade, and reboot into the new system automatically. | # The system should reboot, perform the upgrade, and reboot into the new system automatically. | ||
# Log in to upgraded system, open a terminal, file browser, or other system applications. | # Log in to upgraded system, open a terminal, file browser, or other system applications. | ||
|results= | |results= | ||
# The preupgrade utility will run to completion, without error | # The preupgrade utility will run to completion, without error | ||
# The upgrade should complete and reboot without user assistance. | # The upgrade should complete and reboot without user assistance. | ||
# The user is '''not''' prompted to address low disk space in /boot | # The user is '''not''' prompted to address low disk space in {{filename|/boot}} | ||
# The system should be upgraded to new version without error. | # The system should be upgraded to new version without error. | ||
# The opened terminal, file browser, or other system applications should display and work correctly. | # The opened terminal, file browser, or other system applications should display and work correctly. | ||
}} | }} | ||
[[Category: | [[Category:Obsolete Test Cases]] | ||
Latest revision as of 09:47, 2 May 2013
This test case is obsolete
PreUpgrade has been replaced by FedUp.
PreUpgrade has been replaced by FedUp.
Description
This case tests upgrading a Fedora system from the previous stable release (Fedora 40) to the branched release (Fedora 42) using PreUpgrade.
How to test
- Perform an installation of the stable release (e.g. Fedora 40) with default partitioning (500MB for
/boot). - Do a full system update
- Install
preupgrade - Run
preupgradefrom 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.
- Choose Fedora 42 (Branched) from the list of available upgrade targets, then click Apply.
- When the process completes, click Reboot.
- The system should reboot, perform the upgrade, and reboot into the new system automatically.
- Log in to upgraded system, open a terminal, file browser, or other system applications.
Expected Results
- The preupgrade utility will run to completion, without error
- The upgrade should complete and reboot without user assistance.
- The user is not prompted to address low disk space in
/boot - The system should be upgraded to new version without error.
- The opened terminal, file browser, or other system applications should display and work correctly.