From Fedora Project Wiki
(Suggest a test case) |
(adding category for modularity acceptance test cases) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
|description= This test cases checks that '''dnf''' is able to protect modular packages from being updated when a modular repository is unavailable. According to this dnf [https://bugzilla.redhat.com/show_bug.cgi?id=1616167 bug], it does not remember any information about the origin of the package. So, when the metadata from modular repositories are not available to the system, dnf will override the modular package and will update it to the newest package available in the non-modular repository. | |description= This test cases checks that '''dnf''' is able to protect modular packages from being updated when a modular repository is unavailable. According to this dnf [https://bugzilla.redhat.com/show_bug.cgi?id=1616167 bug], it does not remember any information about the origin of the package. So, when the metadata from modular repositories are not available to the system, dnf will override the modular package and will update it to the newest package available in the non-modular repository. | ||
|setup= | |setup= | ||
# | # To start and learn how to list modules, follow the instructions in [[QA:Testcase_Modularity_module_list|this test case]]. | ||
|actions= | |actions= | ||
| Line 8: | Line 8: | ||
<li>Update your system.<br/> | <li>Update your system.<br/> | ||
<code>dnf update</code></li> | <code>dnf update</code></li> | ||
<li>Install the <code>nodejs</code> | <li>Enable the <code>nodejs</code> module in stream 10. <br/> | ||
<code>dnf module | <code>dnf module enable nodejs:10</code></li> | ||
<li>Install the <code>nodejs</code> module in stream 10. <br/> | |||
<code>dnf module install nodejs:10</code></li> | |||
<li>Update your system with modular repositories disabled. <br/> | <li>Update your system with modular repositories disabled. <br/> | ||
<code>dnf update --disablerepo=\*modular</code></li> | <code>dnf update --disablerepo=\*modular</code></li> | ||
| Line 17: | Line 19: | ||
This test should be considered '''passed''' if: | This test should be considered '''passed''' if: | ||
# All used commands finish without errors. | # All used commands finish without errors. | ||
# The <code>nodejs</code> package will not be updated to a newer version in '''Step 3'''. | # The <code>nodejs</code> package will not be updated to a newer version in '''Step 3''' - the same module and the same stream is listed in the list of installed modules. | ||
|optional= Try different modules. | |optional= Try different modules. | ||
}} | }} | ||
[[Category:Modularity_Acceptance_Test_Cases]] | |||
Latest revision as of 19:15, 10 February 2022
Description
This test cases checks that dnf is able to protect modular packages from being updated when a modular repository is unavailable. According to this dnf bug, it does not remember any information about the origin of the package. So, when the metadata from modular repositories are not available to the system, dnf will override the modular package and will update it to the newest package available in the non-modular repository.
Setup
- To start and learn how to list modules, follow the instructions in this test case.
How to test
- Update your system.
dnf update - Enable the
nodejsmodule in stream 10.
dnf module enable nodejs:10 - Install the
nodejsmodule in stream 10.
dnf module install nodejs:10 - Update your system with modular repositories disabled.
dnf update --disablerepo=\*modular
Expected Results
This test should be considered passed if:
- All used commands finish without errors.
- The
nodejspackage will not be updated to a newer version in Step 3 - the same module and the same stream is listed in the list of installed modules.
Optional
Try different modules.