I tried to run some tests according to documentation and I ran into some problems. Running generated tests doesn't work with this supplied command (from section Schedule Tests and How to write tests:
MODULE=docker avocado run /usr/lib/python2.7/site-packages/moduleframework/modulelint.py ./*.py
Presumably because as of now, that file isn't in that location. I managed to fix it by using this:
MODULE=docker avocado run /usr/lib/python2.7/site-packages/moduleframework/module_framework.py ./*.py
Or, if the intention was to use the modulelint.py, I managed to do that with:
MODULE=docker avocado run /usr/share/moduleframework/tools/modulelint.py ./*.py
Or alternatively, when in the directory, generated tests can be run using:
MODULE=docker avocado run ./*.py
Either way, I think the documentation should be updated with something that is working. I'd create a pull request, but I am not sure what the intention was here, so I'm submitting this as an issue.
Commit fixes the outdated documentation. Thx, though. https://pagure.io/modularity-testing-framework/c/26958fc06c6b37e1ea7ba71bf563b37410a1ddf7?branch=master
Metadata Update from @phracek: - Issue assigned to phracek - Issue close_status updated to: upstream - Issue status updated to: Closed (was: Open)