From Fedora Project Wiki
mNo edit summary |
m (better wording) |
||
Line 8: | Line 8: | ||
|results= | |results= | ||
# Both CLI and graphical update applications should complete the update process with no errors | # Both CLI and graphical update applications should complete the update process with no errors | ||
# Both should check the appropriate repositories for the release | # Both should check the appropriate repositories for the release when testing for updates, with no manual configuration required | ||
# Both should list the number and details of available updates and await confirmation before proceeding with the actual update process | # Both should list the number and details of available updates and await confirmation before proceeding with the actual update process | ||
# Both should correctly install all available updates when you confirm that you wish to do so | # Both should correctly install all available updates when you confirm that you wish to do so | ||
}} | }} | ||
[[Category:Desktop_Acceptance_Test_Cases]] | [[Category:Desktop_Acceptance_Test_Cases]] |
Revision as of 16:26, 19 February 2010
Description
This test case tests whether yum and PackageKit can install package updates.
How to test
- Clean boot the Fedora you wish to test: this could be a system installed from a particular snapshot, pre-release, or release, or a live image. It should be an image for which updates will be available
- Open a console, and run the command
yum update
as root. If you have any difficulty opening a console in the normal fashion from the desktop you are testing, note this, but continue with the test. Complete the update process - If you are testing a live image, reboot. If you are testing an installed system, either wait for more updates to become available, or re-install
- Launch the graphical update application (e.g. system menu > System > Administration > Software Update). Run through the update process
Expected Results
- Both CLI and graphical update applications should complete the update process with no errors
- Both should check the appropriate repositories for the release when testing for updates, with no manual configuration required
- Both should list the number and details of available updates and await confirmation before proceeding with the actual update process
- Both should correctly install all available updates when you confirm that you wish to do so