DevHeads.net

module testing files?

Seeing current modules/* 's files.

Some of the modules have testing files in the directory.
Are the testing files still actually used for the modules?
I assume that only modules/foo/foo.yaml file is required. Other files
like "sources" are meaningless, right?
I think "sources" file is wrongly there.

I just checked my local downloaded modules/* directories.

$ ls */Dockerfile
memcached/Dockerfile mongodb/Dockerfile php/Dockerfile ruby/Dockerfile
$ ls */Makefile
flatpak-runtime/Makefile memcached/Makefile mongodb/Makefile
php/Makefile platform/Makefile ruby/Makefile
$ ls -d */tests
memcached/tests/ mongodb/tests/ php/tests/ ruby/tests/
$ ls -d */sources
eog/sources mariadb/sources mongodb/sources
perl/sources platform/sources python2/sources ruby/sources
flatpak-runtime/sources memcached/sources nodejs/sources
php/sources postgresql/sources python3/sources varnish/sources

I like to see the file structure and testing module is documented or
linked in below page
<a href="https://docs.fedoraproject.org/en-US/modularity/making-modules/" title="https://docs.fedoraproject.org/en-US/modularity/making-modules/">https://docs.fedoraproject.org/en-US/modularity/making-modules/</a>

Comments

Re: module testing files?

By Jun Aruga at 05/07/2019 - 06:41

I think the people who are using or used "meta-test-family" (the
application to test module), has these kind of testing files.

But I faced an installation error on my Fedora 30.
<a href="https://github.com/fedora-modularity/meta-test-family/issues/245" title="https://github.com/fedora-modularity/meta-test-family/issues/245">https://github.com/fedora-modularity/meta-test-family/issues/245</a>

Are you using "meta-test-family" now?
Does it work on your environment?