From Fedora Project Wiki
(Revise for Plasma Discover) |
(KDE: Add a step to go to updates section in Discover) |
||
| Line 10: | Line 10: | ||
#: '''NOTE:''' these specific instructions may be out of date when you read this test case, if they don't seem quite right, just adjust them sensibly. | #: '''NOTE:''' these specific instructions may be out of date when you read this test case, if they don't seem quite right, just adjust them sensibly. | ||
#: In GNOME, open the Overview and launch the '''Software''' application. Click the ''Updates'' button. Click the ''Refresh'' button at top left, if necessary, to find available updates. Click ''Restart & Install''. | #: In GNOME, open the Overview and launch the '''Software''' application. Click the ''Updates'' button. Click the ''Refresh'' button at top left, if necessary, to find available updates. Click ''Restart & Install''. | ||
#: In KDE, open the application menu and launch the '''Discover''' application. Wait for the list of available updates to appear, and click ''Update All''. | #: In KDE, open the application menu and launch the '''Discover''' application. Click the ''Update'' section on the left to view updates. Wait for the list of available updates to appear, and click ''Update All''. | ||
|results= | |results= | ||
# The update process should complete successfully. (Note: it is normal that the graphical update process involves rebooting the system to install the updates and rebooting again once the install is complete). 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. (Note: it is normal that the graphical update process involves rebooting the system to install the updates and rebooting again once the install is complete). 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. | ||
Latest revision as of 02:27, 30 January 2024
Associated release criterion
This test case is associated with the Fedora_41_Beta_Release_Criteria#software-install-remove-update 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_41_Beta_Release_Criteria#software-install-remove-update 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 the system can be updated using a desktop's graphical 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).
- Log into a graphical desktop.
- Run the desktop's graphical updater or package manager (if the update process is a part of the package manager).
- NOTE: these specific instructions may be out of date when you read this test case, if they don't seem quite right, just adjust them sensibly.
- In GNOME, open the Overview and launch the Software application. Click the Updates button. Click the Refresh button at top left, if necessary, to find available updates. Click Restart & Install.
- In KDE, open the application menu and launch the Discover application. Click the Update section on the left to view updates. Wait for the list of available updates to appear, and click Update All.
Expected Results
- The update process should complete successfully. (Note: it is normal that the graphical update process involves rebooting the system to install the updates and rebooting again once the install is complete). 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.