unittest generator and scheduler based on FMF metadata

[jscotka]

unittest dynamic class generator

you can use this class file as dynamic generator for another scheduler like nosetest

$ TARGET=tests/data/Dockerfile nosetests unittest-run.py 
...
----------------------------------------------------------------------
Ran 3 tests in 0.003s

OK

scheduler possibilities

./unittest-run.py --help
Usage: unittest-run.py [OPTIONS] TARGET

Options:
  -c, --checks-paths DIRECTORY  Path to directory containing checks (default
                                ['/home/jscotka/git/colin/colin/checks']).
  -r, --ruleset-dir PATH        Path to a directory with rulesets
  -n, --name TEXT               Select cases by key names
  -f, --filter TEXT             Filter cases based on FMF filter rules
  -v, --verbose INTEGER         change verbosity of unittest scheduler
  --debug                       Enable debugging mode (debugging logs, full
                                tracebacks).
  --help                        Show this message and exit.

usage like:

 $ ./unittest-run.py -v 2 tests/data/Dockerfile 
test (__main__.from_tag_not_latest) ... ok
test (__main__.maintainer_deprecated) ... ok
test (__main__.maintainer_label) ... ok

----------------------------------------------------------------------
Ran 3 tests in 0.002s

OK

[phracek]

Basically, FMF removes python code into fmf (YAML) format. I don't see any advantage for colin alone. Colin functionality, backwards compatibility has to remain. Do not remove python files at all.

I would like to see the other projects which will use FMF. I see only colin uses FMF, like PoC for using FMF, what about to wait till the other project will use/implement it.

[phracek]

I am afraid of using FMF in colin. Once we check Dockerfile, image etc. we have rulesets and we want to check all things.