From Fedora Project Wiki

No edit summary
(make the link to GNOME instructions more visible)
 
(5 intermediate revisions by 2 users not shown)
Line 5: Line 5:
|description=This test case tests whether a graphical desktop notifies the user of available package updates.
|description=This test case tests whether a graphical desktop notifies the user of available package updates.
|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, or enable the ''updates-testing'' repository).
# Log into a graphical desktop.
# Log into a graphical desktop.
# Wait and see whether the system checks for updates, notifies you of their availability, and offers to install them. The time before the first notification appears varies, and can be up to an hour or more: you may want to leave the test system sitting for a while and do something else, or run some other tests while waiting for the notification. For GNOME, see the tip below to reduce the wait time.
# Wait and see whether the system checks for updates and notifies you of their availability. The time before the first notification appears varies, and can be up to an hour or more: you may want to leave the test system sitting for a while and do something else, or run some other tests while waiting for the notification.
{{admon/tip|Tip for shortening the waiting time to the updates notification on GNOME|On the GNOME desktop, you can run the following commands to shorten the waiting time:  
#* You can run command {{command|pkmon}} to monitor what's going on in the background (e.g. downloading updates -- the notification is shown only after all updates have been downloaded).
{{admon/tip|Tip: Speed up the notification on GNOME|You can see instructions to shorten the waiting time in GNOME at [[QA:Testcase Gnome software update preparation]].}}
{{admon/tip|Tip: Speed up the notification on KDE|On the KDE desktop, you can run the following command to shorten the waiting time:  
<pre>
<pre>
$ gsettings set org.gnome.software check-timestamp $(date '+%s' --date='18:00 2 days ago')
rm ~/.config/plasma-pk-updates
$ gsettings set org.gnome.software install-timestamp $(date '+%s' --date='08:00 8 days ago')
$ sudo touch --no-create --date='08:00 8 days ago' /var/lib/PackageKit/offline-update-competed
</pre>
</pre>
You should reboot or log out and back in after changing these settings. The notification should now appear within ten minutes, but it's best to give it a bit longer to be sure. Use the command {{command|pkmon}} to monitor what's going on in the background (e.g. downloading updates -- the notification is shown only after all updates have been downloaded).}}
You should reboot or log out and back in. The notification should now appear within ten minutes, but it's best to give it a bit longer to be sure.}}
|results=
|results=
# The desktop should notify you that updates are available and provide an obvious action to install them.
# The desktop should notify you that updates are available and provide an obvious action to install them.
}}
}}
[[Category:Desktop_Acceptance_Test_Cases]]
[[Category:Desktop_Acceptance_Test_Cases]]
[[Category:Critical_path_test_cases]]
[[Category:Critical_path_test_cases]]

Latest revision as of 13:30, 18 October 2022

Note.png
Associated release criterion
This test case is associated with the Fedora_41_Final_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 a graphical desktop notifies the user of available package updates.


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, or enable the updates-testing repository).
  2. Log into a graphical desktop.
  3. Wait and see whether the system checks for updates and notifies you of their availability. The time before the first notification appears varies, and can be up to an hour or more: you may want to leave the test system sitting for a while and do something else, or run some other tests while waiting for the notification.
    • You can run command pkmon to monitor what's going on in the background (e.g. downloading updates -- the notification is shown only after all updates have been downloaded).
Idea.png
Tip: Speed up the notification on GNOME
You can see instructions to shorten the waiting time in GNOME at QA:Testcase Gnome software update preparation.
Idea.png
Tip: Speed up the notification on KDE
On the KDE desktop, you can run the following command to shorten the waiting time: 
rm ~/.config/plasma-pk-updates
You should reboot or log out and back in. The notification should now appear within ten minutes, but it's best to give it a bit longer to be sure.

Expected Results

  1. The desktop should notify you that updates are available and provide an obvious action to install them.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_desktop_update_notification&oldid=657773"