UX review

[bkabrda]

This is a proposal created in reaction to [1].

As a user of MTF, I would ideally like to just run a single command, let's call it mtf, in the module directory and everything would just work. The approach proposed in [1] is too complex and somewhat clumsy from user perspective.

The mtf command could work like this:

• The config.yaml file would contain default list of modules (i.e. the current MODULE argument) which to test against (e.g. ["docker", "rpm"])
• User would run mtf.
  • This would first invoke the functionality currently covered by mtf-generator
  • And then it would invoke the python -m avocado ... part.
• Furthermore, mtf could accept various arguments, such as override for the set of modules which to test against (i.e. the current MODULE argument), subset of test files to run etc.

If the user wants to create a Makefile, they would just put mtf --some-options in it and they'd be done with that. They wouldn't need to create unnecessary Makefiles, which would mostly contain the same lines for every module.

Does this sound reasonable? I believe it would greatly improve UX to have this.

[1] http://modularity-testing-framework.readthedocs.io/en/latest/user_guide/index.html

[phracek]

Make sense to me. Keep it simple.

The config.yaml file would contain default list of modules

Can you please explain it a bit more? modulemd.yaml file contains all default list of modules.

If the user wants to create a Makefile, they would just put mtf --some-options in it and they'd be done with that. They wouldn't need to create unnecessary Makefiles, which would mostly contain the same lines for every module.

The Makefile was present because of automation tasks. Just run make test and not mtf.
I guess, it is more logical.
But I agree with you, creating Makefiles is painful for first time when you play with modules / containers.

Does this sound reasonable? I believe it would greatly improve UX to have this.
[1] http://modularity-testing-framework.readthedocs.io/en/latest/user_guide/index.html

+1

[bkabrda]

Can you please explain it a bit more? modulemd.yaml file contains all default list of modules.

I meant this simply as a replacement for what was previously in the Makefile. In other words, if currently a Makefile's test section says that the module should be tested for RPM and Docker, then that's what should be possible to put into the config (I think the term "module" is overloaded in this sense, hence the misunderstanding).