From Fedora Project Wiki
(activate categories) |
(remove yum instructions) |
||
Line 4: | Line 4: | ||
|actions= | |actions= | ||
# 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 (or you can downgrade a package after installation). | # 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 (or you can downgrade a package after installation). | ||
# Open a console, and run the command {{command|dnf update}} as root | # Open a console, and run the command {{command|dnf 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 encounter dependency problems, ensure a bug is reported for the issue, and try with a different package. | ||
|results= | |results= | ||
# The update process should complete successfully. Errors caused by packaging bugs should be reported to the individual packages, but would not usually count as release-blocking bugs in the updater itself. | # The update process should complete successfully. Errors caused by packaging bugs should be reported to the individual packages, but would not usually count as release-blocking bugs in the updater itself. |
Revision as of 11:39, 23 March 2016
Description
This test case tests whether the system can be updated using the default console package manager.
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 (or you can downgrade a package after installation).
- Open a console, and run the command
dnf 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 encounter dependency problems, ensure a bug is reported for the issue, and try with a different package.
Expected Results
- The update process should complete successfully. Errors caused by packaging bugs should be reported to the individual packages, but would not usually count as release-blocking bugs in the updater itself.