From Fedora Project Wiki
(Created page with "{{Template:Associated_release_criterion|Alpha|updates}} {{Template:Associated_release_criterion|Beta|updates}} {{Template:Associated_release_criterion|Beta|update-notification...") |
No edit summary |
||
| Line 2: | Line 2: | ||
{{Template:Associated_release_criterion|Beta|updates}} | {{Template:Associated_release_criterion|Beta|updates}} | ||
{{Template:Associated_release_criterion|Beta|update-notification}} | {{Template:Associated_release_criterion|Beta|update-notification}} | ||
{{QA/Test_Case | {{QA/Test_Case | ||
Revision as of 15:31, 15 July 2014
Associated release criterion
This test case is associated with the Basic_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Basic_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_Beta_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#update-notification release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_Beta_Release_Criteria#update-notification release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Description
This test case tests whether yum can check for and install package updates from the command line.
How to test
Live Environments
This test is not intended to be run on Live images.
This test is not intended to be run on Live images.
- Clean boot the Fedora you wish to test: this could be a system installed from a particular snapshot, pre-release, release, or a cloud image. It should be an image for which updates will be available.
- Otherwise, open a console, and run the command
yum updateas 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 encounter dependency problems, ensure a bug is reported for the issue, and try again with the --skip-broken parameter - Wait for more updates to become available, manually downgrade some packages so updates for them are again available, or re-install
Expected Results
- yum should complete the update process with no errors
- yum should check the appropriate repositories for the release when testing for updates, with no manual configuration required
- yum should list the number and details of available updates and await confirmation before proceeding with the actual update process
- yum should correctly install all available updates when you confirm that you wish to do so. Note that a failure caused by problems with the packages in the repositories, rather than yum or PackageKit misbehaving, should be reported against the offending package(s) and considered a 'warn', rather than 'fail', if you are performing desktop validation testing