From Fedora Project Wiki

m (Minor save)
m
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description= This test case will show if modularity is enabled in Fedora and that the system provides basic information about the available modules.  
+
|description= This test case will show if modularity is enabled and that the system provides basic information about the available modules.  
 
|setup=  
 
|setup=  
# Install any of the Fedora spins, for example ''Workstation'' or ''Server''.
+
# Install Fedora. Modularity is available for all varieties of Fedora and it should be switched on by default. For the start, you could choose ''Fedora Workstation'' or '' Fedora Server''.
# Log onto the system.
+
# Log onto the system.  
# Run a terminal application, such as '''gnome-terminal'''. The following test will use '''dnf''' to work with the modules.
+
# Run a terminal application, such as '''gnome-terminal''', or switch to a virtual console ('''Ctrl-Alt-F3'''). The following test will use '''dnf''' to work with the modules.
 
'''Note:''' For the time's being, users can work with modules using '''dnf'''. In the future, other package managers will be able to deal with it. Until then, do not attempt to test this approach using tools other than '''dnf'''.
 
'''Note:''' For the time's being, users can work with modules using '''dnf'''. In the future, other package managers will be able to deal with it. Until then, do not attempt to test this approach using tools other than '''dnf'''.
  
 
|actions=
 
|actions=
 
<ol>
 
<ol>
  <li>Check that '''dnf''' provides you with the list of '''all''' modules available to the system: <br/>
+
  <li>Check that '''dnf''' provides you with a list of '''all''' modules available to the system: <br/>
 
       To do so, execute <code> dnf module list</code>.  You can also use the <code>--all</code> option, the results should be the same.<br/></li>
 
       To do so, execute <code> dnf module list</code>.  You can also use the <code>--all</code> option, the results should be the same.<br/></li>
  <li>Check that '''dnf''' provides you with the list of modules that have been '''enabled''' on the system.  <br/>
+
  <li>Check that '''enabled''' modules can be listed.  <br/>
       Execute <code>dnf module list --enabled</code>.</li>
+
       Execute <code>dnf module list --enabled</code> to get the list.</li>
  <li></li>
+
  <li>Check '''disabled''' modules can be listed. <br/>
<li></li>
+
      Execute <code>dnf module list --disabled</code> to get the list.</li>
  <li></li>
+
  <li>Check that '''dnf''' provides you with a list of modules that are '''installed''' on the system. <br/>
<ol>
+
      Execute <code>dnf module list --installed</code> to get the list.</li>
 
+
</ol>
 
 
=== Listing All Enbaled Modules: ===
 
    # Execute <code> dnf module list --enabled </code>
 
 
 
=== Listing All Disabled Modules: ===
 
    # Execute <code> dnf module list --disabled </code>
 
 
 
=== Listing All Installed modules ===
 
    # Execute <code> dnf module list --installed </code>
 
  
 
|results=
 
|results=
The commands execute without error  
+
# Modularity and modular repositories should be enabled by '''default'''. If it for does not work for any reason, the test should be considered a '''fail'''.
# The first command prints all the modules with their stream, version and profile details.
+
# All above commands must run without any errors and they should provide the needed info. If they throw any error, report a bug, and the test '''fails'''.
# The second command prints all the modules which are enabled in the system
+
# <code>dnf module list (--all)</code> lists all modules and provides details, such as stream, version and profile. If this command returns an empty list, the test should be considered a '''fail'''.
# The third command prints all the modules which are presently disabled
+
# <code>dnf module list --enabled</code> lists all enabled modules. The result can be an empty list, if there are no enabled modules.
# The fourth command prints all the modules which are presently installed  
+
# <code>dnf module list --disabled</code> lists all disabled modules. The result can be an empty list, if there are no disabled modules.
|optional=Optionally provide hints for exploratory testing.
+
# <code>dnf module list --installed</code> lists all installed modules. The result can be an empty list, if there are no installed modules.
 
}}
 
}}

Latest revision as of 11:06, 1 March 2019

Description

This test case will show if modularity is enabled and that the system provides basic information about the available modules.

Setup

  1. Install Fedora. Modularity is available for all varieties of Fedora and it should be switched on by default. For the start, you could choose Fedora Workstation or Fedora Server.
  2. Log onto the system.
  3. Run a terminal application, such as gnome-terminal, or switch to a virtual console (Ctrl-Alt-F3). The following test will use dnf to work with the modules.

Note: For the time's being, users can work with modules using dnf. In the future, other package managers will be able to deal with it. Until then, do not attempt to test this approach using tools other than dnf.

How to test

  1. Check that dnf provides you with a list of all modules available to the system:
    To do so, execute dnf module list. You can also use the --all option, the results should be the same.
  2. Check that enabled modules can be listed.
    Execute dnf module list --enabled to get the list.
  3. Check disabled modules can be listed.
    Execute dnf module list --disabled to get the list.
  4. Check that dnf provides you with a list of modules that are installed on the system.
    Execute dnf module list --installed to get the list.

Expected Results

  1. Modularity and modular repositories should be enabled by default. If it for does not work for any reason, the test should be considered a fail.
  2. All above commands must run without any errors and they should provide the needed info. If they throw any error, report a bug, and the test fails.
  3. dnf module list (--all) lists all modules and provides details, such as stream, version and profile. If this command returns an empty list, the test should be considered a fail.
  4. dnf module list --enabled lists all enabled modules. The result can be an empty list, if there are no enabled modules.
  5. dnf module list --disabled lists all disabled modules. The result can be an empty list, if there are no disabled modules.
  6. dnf module list --installed lists all installed modules. The result can be an empty list, if there are no installed modules.