Skip to content

QA:Testcase Module Streams

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#packages-and-module-installation release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.


This test case takes care of testing the module streams, that they are all installable, all available and working as expected.


For this tests you will need to install every module stream on its own, so it's the best to setup a new system which gets snapshoted after the initial setup. After that it can be rolled back for every module install.

It's enough to setup a system with the Minimal Install group.

How to test

  1. Login to the machine
  2. Get a list of all module streams and compare it to the stream list from RHEL and to the source in Git source repo
  3. The easiest way to test all streams is to install the package groups in the individual streams, i.e. for postgresql:
dnf module install postgresql
dnf module install postgresql:13
dnf module install postgresql:13/client

Repeat step 3 as often as module streams and package groups are available.

This could be automated with i.e. Ansible to do all the install -> rollback -> install -> rollback -> ... and emiting the output via Ansible.

Expected Results

All module streams should be available and there shouldn't be any errors while installing any of the package groups of the individual streams. (some of the installs will show warnings though because they are incompatible with other streams)

Additional Information

If you have questions with respect to this content or to report concerns regarding the use or misuse content please do not hesitate to contact us at

Rocky Linux and the Rocky Enterprise Software Foundation (RESF) does not make any express or implied warranties, including but not limited to the warranties of non-infringement of any third party intellectual property rights. RESF does not warrant that any pending trademark applications for trademarks of RESF will result in any granted trademark protection. RESF shall not be liable for any claims relating to user's activities falling within the scope of the permission and user hereby agrees to indemnify, defend and hold RESF and its contributors harmless against any such claim.

This work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.