# 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.

# 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.

# Do a full system update and reboot

# Do a full system update and reboot

−

# Install {{package|fedup}}

+

# Install {{package|fedup}}. It is usually a good idea to install the very latest version from ''updates-testing'': {{command|su -c 'yum --enablerepo=updates-testing install fedup'}}

−

#* Be sure to get the latest release, this may involve enabling updates-testing (put <code>--enablerepo=updates-testing</code> between {{command|yum}} and {{command|install}} on the command line)

+

−

#* '''2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.'''

+

# Find the URL of the development branch for {{FedoraVersion|long|next}}. This URL should be of the form <nowiki>http://dl.fedoraproject.org/pub/fedora/linux/development/<version>/<arch>/os/</nowiki>

# Find the URL of the development branch for {{FedoraVersion|long|next}}. This URL should be of the form <nowiki>http://dl.fedoraproject.org/pub/fedora/linux/development/<version>/<arch>/os/</nowiki>

#* <version> is the of fedora under test (currently {{FedoraVersion||next}})

#* <version> is the of fedora under test (currently {{FedoraVersion||next}})

#* <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)

#* <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)

−

#* Due to the way that branced composes are done, the fedup client is not capable of grabbing initrd and kernel from those branches. The devel branch will rebuild from whatever is in stable for every push to the devel stable branch.

+

#* Due to the way that branched composes are done, the fedup client is not capable of grabbing initrd and kernel from those branches. The devel branch will rebuild from whatever is in stable for every push to the devel stable branch.

#* <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds

#* <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds

−

# Check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}

+

# Check the {{filename|fedupdebug.log}} file to see if any errors show up in the output from {{command|fedup-cli}}

−

# Reboot the system if {{command|fedup-cli}} has completed without error.

+

# Reboot the system if {{command|fedup-cli}} has completed without error

−

# Once the system reboots, there should be a new entry in the GRUB menu titled {{command|System Upgrade}}.

+

# Once the system reboots, there should be a new entry in the GRUB menu titled {{command|System Upgrade}}

# Select the {{command|System Upgrade}} option from the GRUB menu

# Select the {{command|System Upgrade}} option from the GRUB menu

−

#* If you want to be able to see progress during the upgrade, append <code>plymouth.splash=fedup</code> to the end of the kernel parameters

# The system should boot into the upgrade process and a fedup progress screen should be displayed

# The system should boot into the upgrade process and a fedup progress screen should be displayed

#* Press the <ESC> key, will switch from the graphical progress screen to the textual progress information display

#* Press the <ESC> key, will switch from the graphical progress screen to the textual progress information display

−

#** Returning to the graphical progress screen by pressing the <ESC> key will return you to a screen where the progress bar is "frozen" {{bz|873144}} and {{bz|883075}}, exist for this and other previous display issues related to fedup. Remove this comment once the bugs are confirmed fixed.

+

#** Returning to the graphical progress screen by pressing the <ESC> key will return you to a screen where the progress bar is "frozen" {{bz|873144}} and {{bz|883075}}, exist for this and other previous display issues related to fedup. Remove this comment once the bugs are confirmed fixed

# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|next}} will be on the grub menu

# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|next}} will be on the grub menu

# 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.

Line 33:

Line 30:

# {{command|fedup-cli}} will run to completion, without error

# {{command|fedup-cli}} will run to completion, without error

# The upgrade process should complete and reboot without user assistance beyond selecting {{command|System Upgrade}} from the GRUB menu

# The upgrade process should complete and reboot without user assistance beyond selecting {{command|System Upgrade}} from the GRUB menu

−

# 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

#* Running through the [[Test_Results:Current_Desktop_Test|desktop test cases]] would be a good for verification.

#* Running through the [[Test_Results:Current_Desktop_Test|desktop test cases]] would be a good for verification.

}}

}}

[[Category:Upgrade_system]]

[[Category:Upgrade_system]]

[[Category:Package_preupgrade_test_cases]]

[[Category:Package_preupgrade_test_cases]]

Revision as of 00:09, 15 March 2013

Draft Test Case for New SoftwareThis test case is very new and may still have errors. Fedup is also new software and this procedure may change. Please ask questions if anything is not clear and let us know if there are problems

Description

This case is for upgrading using to upgrade the current release (Fedora 25) to the branched release (Fedora 26) using the Fedup CLI.

How to test

Perform an installation of the stable release (e.g. Fedora 25) with default partitioning (no less than 500MB for /boot), selecting the default package set.

Do a full system update and reboot

Install fedup. It is usually a good idea to install the very latest version from updates-testing: {{{1}}}

Find the URL of the development branch for Fedora 26. This URL should be of the form http://dl.fedoraproject.org/pub/fedora/linux/development/<version>/<arch>/os/

<version> is the of fedora under test (currently 26)

<arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)

Due to the way that branched composes are done, the fedup client is not capable of grabbing initrd and kernel from those branches. The devel branch will rebuild from whatever is in stable for every push to the devel stable branch.

<URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds

Check the fedupdebug.log file to see if any errors show up in the output from fedup-cli

Reboot the system if fedup-cli has completed without error

Once the system reboots, there should be a new entry in the GRUB menu titled System Upgrade

Select the System Upgrade option from the GRUB menu

The system should boot into the upgrade process and a fedup progress screen should be displayed

Press the <ESC> key, will switch from the graphical progress screen to the textual progress information display

Returning to the graphical progress screen by pressing the <ESC> key will return you to a screen where the progress bar is "frozen" RHBZ #873144 and RHBZ #883075, exist for this and other previous display issues related to fedup. Remove this comment once the bugs are confirmed fixed

Once the upgrade process has completed, the system will reboot and an option to boot Fedora 26 will be on the grub menu

Log in to upgraded system, open a terminal, file browser, or other system applications.

Expected Results

fedup-cli will run to completion, without error

The upgrade process should complete and reboot without user assistance beyond selecting System Upgrade from the GRUB menu

The system should be upgraded to new version without error

The opened terminal, file browser, or other system applications should display and work correctly