From Fedora Project Wiki

Revision as of 20:44, 26 July 2018 by Adamwill (talk | contribs) (update associated criterion template)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Associated release criterion
This test case is associated with the Fedora_40_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 tests whether the system can be updated using a desktop's graphical package manager.

How to test

  1. 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).
  2. Log into a graphical desktop.
  3. 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 Kicker and launch the Apper application. Double click Updates. Wait for the list of available updates to appear, and click Apply.

Expected Results

  1. The update process should complete successfully. (Note: it is usual that the GNOME 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.