From Fedora Project Wiki
(Created page with "{{Template:Associated_release_criterion|Basic|package install remove}} {{QA/Test_Case |description=This test case tests whether a given package manager (it can be used to tes...")
 
No edit summary
 
(22 intermediate revisions by the same user not shown)
Line 2: Line 2:


{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests whether a given package manager (it can be used to test any package manager) can properly install and remove packages.
|description=This tests whether one of the available package managers provided in the Install step below can properly install and remove packages.
|setup=
|setup=
# Install or deploy the Fedora release media you wish to test. You can use any allowed configuration by the installer.
# Install the Fedora pre-release version you wish to test. You can use any configuration allowed by the installer.
# Reboot to the installed system.
# Reboot to the installed system. and complete any first boot procedure(s).
|actions=
|actions=
# On the installed system, search for disk mount/unmount errors using the following command: <pre>sudo journalctl -b | grep -E 'dirty bit|data may be corrupt|recovery|unmounted|recovering'</pre> If there is no output, there were no such errors and everything seems correct.
# Using the package manager you prefer install two packages. Installing packages you are familiar with is recommended. Check the following:
#* If there was some output from the grep command, save the full journal log using <pre>sudo journalctl -b > journal.log</pre> If the grep output does not show clearly that the output is related to a disk mount/unmount problem, open the {{filename|journal.log}} file, find the relevant lines and verify whether this is an error related to disk mounting or an unrelated message.
#* If there were errors during the install other that repository problems, please file a bug report.
#* If the output is related to disk mounting, please file a bug report (the {{pkg|kernel}} is most likely the correct package to file the report against) and attach the {{filename|journal.log}} file to the bug report.
#* Verify that both packages you installed will start and close normally. If one or both applications will not start and close nornally, please file a bug report.
# Restart the system.
# Using the same package manager you used for step 1, remove the packages installed in step 1 and watch for any error messages in the process. Check the following:
# Repeat all the steps above once more (the first pass checks whether the system unmounted disks properly when rebooting from the installer, the second pass checks whether the system unmounted disks properly when rebooting from the installed system).
#* If there were errors during the removal, please file a bug report.
 
#* Check that the applications are no longer present using the command: {{command|rpm -q package1 package2}}. If one or both packages are still present, please file a bug report.
{{admon/note|Manual error checking|This test relies on specific expected text in error messages. It's possible these messages may change in the future and there may be an error that is not caught by the {{command|grep}} command. Optionally you can examine the {{command|sudo journalctl -b}} output manually for error messages that might indicate a filesystem not being cleanly unmounted at shutdown, and file a bug report if you find any. Here are sample error messages from system journal that indicate errors known to us:
<pre>
# FAT fsck
systemd-fsck[681]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
 
# FAT kernel
FAT-fs (vdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
 
# ext4 fsck
systemd-fsck[681]: /dev/vdb2: recovering journal
 
# ext4 kernel
EXT4-fs (vdb2): recovery complete
 
# xfs kernel
XFS (vdb3): Starting recovery (logdev: internal)
</pre>}}
|results=
|results=
# Each {{command|grep}} command should produce no output.
# The applications should install without errors.
# Requesting reboot should cause an orderly shutdown and restart of the system.
# The applications should start and close without errors.
# The applications should be removed without errors.
}}
}}

Latest revision as of 15:00, 7 February 2020

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#package install remove 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 tests whether one of the available package managers provided in the Install step below can properly install and remove packages.

Setup

  1. Install the Fedora pre-release version you wish to test. You can use any configuration allowed by the installer.
  2. Reboot to the installed system. and complete any first boot procedure(s).

How to test

  1. Using the package manager you prefer install two packages. Installing packages you are familiar with is recommended. Check the following:
    • If there were errors during the install other that repository problems, please file a bug report.
    • Verify that both packages you installed will start and close normally. If one or both applications will not start and close nornally, please file a bug report.
  2. Using the same package manager you used for step 1, remove the packages installed in step 1 and watch for any error messages in the process. Check the following:
    • If there were errors during the removal, please file a bug report.
    • Check that the applications are no longer present using the command: rpm -q package1 package2. If one or both packages are still present, please file a bug report.

Expected Results

  1. The applications should install without errors.
  2. The applications should start and close without errors.
  3. The applications should be removed without errors.



Retrieved from "https://fedoraproject.org/w/index.php?title=User:Tablepc/Draft_Testcase_package_install_remove&oldid=565592"