From Fedora Project Wiki

(Rewrite module installation test)
mNo edit summary
Line 2: Line 2:
|description=This test case proves that a module can be installed on the system.
|description=This test case proves that a module can be installed on the system.
|setup=To test this feature:
|setup=To test this feature:
# Install a '''clean''' Fedora 30 or newer.  
# Install a '''clean''' Fedora.  
|actions=
|actions=
# Open a terminal session, either use '''gnome-terminal''' or a virtual console.
# Open a terminal session, either use terminal or a virtual console.
# List available modules using <code>dnf module list</code> and choose one of them to do the next step. Find out if the module has a '''default stream''' and a '''default profile''' set. Based on this, follow one of the scenarios. When you attempt to install a module without  a default stream or profile, omitting to specify the stream or profile in the installation command will only result in enabling that module. Pay attention to this and always use the appropriate command.
# List available modules using <code>dnf module list</code> and choose one of them to do the next step. Find out if the module has a '''default stream''' and a '''default profile''' set. Based on this, follow one of the scenarios. When you attempt to install a module without  a default stream or profile, omitting to specify the stream or profile in the installation command will only result in enabling that module. Pay attention to this and always use the appropriate command.
# Install a module with default stream and profile:
# Install a module with default stream and profile:

Revision as of 11:27, 11 March 2019

Description

This test case proves that a module can be installed on the system.

Setup

To test this feature:

  1. Install a clean Fedora.

How to test

  1. Open a terminal session, either use terminal or a virtual console.
  2. List available modules using dnf module list and choose one of them to do the next step. Find out if the module has a default stream and a default profile set. Based on this, follow one of the scenarios. When you attempt to install a module without a default stream or profile, omitting to specify the stream or profile in the installation command will only result in enabling that module. Pay attention to this and always use the appropriate command.
  3. Install a module with default stream and profile:
    1. Install the module using dnf module install <module>.
  4. Install a module without a default stream, or choose a non-default stream:
    1. Install the module using dnf module install <module>:<stream>.
  5. Install a module without a default profile, or choose a non-default profile:
    1. Install the module using dnf module install <module>:<stream>/<profile>.
  6. List the enabled modules dnf module list --enabled.
  7. List the installed modules dnf module list --installed.
  8. Check that packages were really installed rpm -qa <module>.
  9. If the installed module was an application or a service, try to run it.

Expected Results

The following requirements must be met:

  1. All installation commands must run without errors.
  2. All installation commands must result in packages installed on the system.
  3. The installed module must be listed in both --enabled and --installed lists.
  4. rpm -qa <module> must return the installed package with the same version as declared by the module.
  5. If the module was an application or a service, it should attempt to start.
  6. Using dnf module install <module>:<stream> should be enough to install every module.

Note: All modules should have a default profile and they should be able to install using dnf module install <module>:<stream>. If a module does not have a default profile set, report a bug for it.



Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Modularity_install_module&oldid=536156"