This test case tests that the modules have the required defaults set.
- Make sure you have a clean installation of Fedora (all flavors are possible).
- Log onto the system as a superuser or a user with sudo rights.
- Run a terminal application, such as gnome-terminal, or switch to a virtual console (Ctrl-Alt-F3). The following test is based on the DNF package manager.
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
- List available modules:
dnf module list.
- Check for module streams. The stream column of a listed module must not be empty, i.e. there must be at least one stream for each listed module available. The module does not need to have a default stream, marked
[d], as default streams are not required. However, it can have one.
- Check for profiles. The profile column of a listed module must not be empty, i.e. there must be at least one profile available for every stream. There might be more profiles available.
- Check for defaults profiles. For every module stream, there must be one, and only one, default profile, marked
- For every examined module, check the detailed info, too.
dnf module list <module>and see if the information corresponds with the previous information.
- Check that the module can be installed using the following command:
dnf module install <module>:<stream>, but do not explicitly provide any profile.
- Check that the module has been successfully installed.
dnf module list --installed.
- The listed module provides at least one stream.
- The listed module provide at least one profile for each stream.
- For each module stream, at least one profile is marked as default.
- The detailed information corresponds with the information in the overview.
- The module's stream can be installed without explicitly providing the profile.
- The module is installed with the selected stream and its default profile.
- Currently (August 2019), some modules do not have (default) profiles set, because their creators decided that they are not meant to be installed, they only provide dependencies. However, the good practice is that such modules do have a default profile, too. In this case, the default profile should be empty, i.e. not provide any packages to install and therefore the installation part of this test case will not succeed. If not sure, check with the module's creator.
- If the above described operations do not succeed and the reported error seems to be a modular problem, i.e. a missing profile or stream, broken dependencies, and similar, then please report a bug against this particular module in Fedora Modules.
- If the problem seems to be DNF related, the file a bug against DNF.