Would be perfect to be able to check whole base config yaml.file (for all module types),
and in case ENV variables are set too, then check also with these variables set,
like MODULE, CONFIG, MODULEMDURL, URL, ... what redefines values inside config.yaml or allows run just selected module tests.

for implementating this see these low level functions in https://pagure.io/modularity-testing-framework/blob/master/f/moduleframework/module_framework.py
like: get_correct_url()

and use or improve class CommonFunctions what is intended for config parsing and is used for inheritance of testing classes

Please consider also check following directives:

• FROM baseruntime/baseruntime
• check for installing modules in images using microdnf

Check that modulemd points users to relevant documentation sources. For example this one points to outdated/too generic places (both community and documentation):

references: {community: 'https://fedoraproject.org/wiki/Modularity', documentation: 'https://fedoraproject.org/wiki/Fedora_Packaging_Guidelines_for_Modules',

"community" should in all cases point to https://docs.pagure.org/modularity/
"documentation" should ideally point to a specific component repo in container-images until we decide something else.

Please consider also check following directives:

• FROM baseruntime/baseruntime
• check for installing modules in images using microdnf

Pull Request which covers this issue is https://pagure.io/modularity-testing-framework/pull-request/67

PR is merged. Closing the issue.