QA:Testcase upgrade fedup cli previous desktop encrypted

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(create an encrypted upgrade test case based on the desktop one (with a few tweaks I'll copy to the desktop one))
 
(use admon template for the warning)
Line 9: Line 9:
 
# Typical desktop applications should display and work correctly
 
# 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 good for verification
#* If you encounter an issue that does not seem related to encryption, perform the simpler [[QA:Testcase_upgrade_fedup_cli_previous_desktop]] test case - which is just this test case without encryption - and verify the problem occurs in that case too. If so, consider it a failure of that test case, not this one.
+
{{admon/important|Failures not related to encryption|If you encounter an issue that does not seem related to encryption, perform the simpler [[QA:Testcase_upgrade_fedup_cli_previous_desktop]] test case - which is just this test case without encryption - and verify the problem occurs in that case too. If so, consider it a failure of that test case, not this one.}}
 
}}
 
}}
 
[[Category:Upgrade_system]]
 
[[Category:Upgrade_system]]
 
[[Category:Package_fedup_test_cases]]
 
[[Category:Package_fedup_test_cases]]

Revision as of 00:43, 15 March 2013

Description

This test case tests upgrading from the current release (Fedora 21) to the branched release (Fedora 22) using the Fedup CLI with the default desktop package set and encryption.


How to test

  1. Perform an installation of the stable release (e.g. Fedora 21) with default partitioning (no less than 500MB for /boot), selecting the default package set, or using the default live image, and enabling storage encryption during installation.
  2. Do a full system update and reboot
  3. Install the latest version of Package-x-generic-16.pngfedup from the stable or updates repository
  4. 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-20141216/rawhide/(arch)/os - replace (arch) with the correct arch
  5. Start the upgrade prep by executing:
    • sudo fedup --network <version> --instrepo <URL> (--product=<desired product>)
    • <version> is the version of Fedora you are upgrading to (currently 22)
    • <URL> is the location found in the previous step
    • <desired product> is the Fedora Product you want to upgrade to ('workstation' if you had GNOME installed, for example). This must be specified for upgrades from releases before Fedora 21 to Fedora 21 or later
  6. If you need to use a local mirror to test a brand new change, start the upgrade prep by executing the following command:
    • su -c '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 the <ESC> key 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. Accessing the encrypted storage volume(s) should work normally after the upgrade
  5. Typical desktop applications should display and work correctly
Important.png
Failures not related to encryption
If you encounter an issue that does not seem related to encryption, perform the simpler QA:Testcase_upgrade_fedup_cli_previous_desktop test case - which is just this test case without encryption - and verify the problem occurs in that case too. If so, consider it a failure of that test case, not this one.