|
||
|
||
|
||
|
||
|
||
|
||
|
||
pingou commented 7 years ago | ||
|
||
|
||
|
||
|
||
|
||
|
||
pingou commented 7 years ago
| ||
HI @stefw
I've cteated PoC how MTF can be integrated into ansible.
It schedule tests via special script run-them, what is able to handle various modules and koji builds for modules (actually trigerred by MBS change messages (status done))
If you would like, I can copy tests here, to have tests explicitly here and run then explicitly via avocado, not via magic run-them.sh
script :-)
it is done in this run-them.sh
script steps like:
parse module build set enviromental variables avocado run /usr/share/moduleframework/examples/testing-module/*
I've created this PR as an feedback for section: Example: Modularity testing Framework
on page https://fedoraproject.org/wiki/Changes/InvokingTestsAnsible
For me it is working well and ansible could be used for invocation MTF tests very simple.
Actually there is just issue and it is how to interpret results, there could be something what is able to parse for example xunit output, or tap output, or whatever what avocado framework is able to produce.
Tests are scheduled by avocado as whole testsuite. I do not expect to run tests sepatatelly, to have there more ansible 'phases' with unique tests, but it is also possible to list tests and then run them separately, change command (you have to imagine that it is ansible 'for' loop :-)):
avocado run /usr/share/moduleframework/examples/testing-module/* -> for foo in /usr/share/moduleframework/examples/testing-module/*; do avocado run $foo done
While fine for the moment, this would be something that we would need to document if we allow or not. COPR by nature can be very volatile so I would be not in favor of allowing it.
But that is something to worry about later, this is fine for now :)