I want to use ansible-community/ansible-test-gh-action action to have less boilerplate code for CI (prepare venv etc).
I created a new workflow file for this - I do not want to break existing CI.
sanity and units tests do not need self-hosted runner (thank you for noticing @shoriminimoe)
use matrix test
The tests are run in docker containers, as this is default. Before this we didn't run sanit tests on ansible 2.14. Now we do run them, and some sanity tests required small code fixes. Similar, we didn't run unit tests with ansible 2.9, now we do, again small fixes were needed in the tests.
Sanity tests are run only for latest 3 ansible versions (2.12 to 2.14), on only one python version. I do not see need to cover combinations. In addition, pylint in ansible2.9 complained about whitespaces that later versions do not. This was most likely a bug in particular pylint/ansible-test version. Best to not even run this one.
`
Units test are run for all ansible/python version that collection is supposed to support. This should detect if we use some very recent python language feature, or import library that is not available yet in say python 3.8.
Integration tests - the PR does not yet touch them. Will be done later, I want first to get feedback on this one, and hopefully also merge it.
I want to use ansible-community/ansible-test-gh-action action to have less boilerplate code for CI (prepare venv etc). I created a new workflow file for this - I do not want to break existing CI.
I used parts of @shoriminimoe !matrix-testing branch:
The tests are run in docker containers, as this is default. Before this we didn't run sanit tests on ansible 2.14. Now we do run them, and some sanity tests required small code fixes. Similar, we didn't run unit tests with ansible 2.9, now we do, again small fixes were needed in the tests.
Sanity tests are run only for latest 3 ansible versions (2.12 to 2.14), on only one python version. I do not see need to cover combinations. In addition, pylint in ansible2.9 complained about whitespaces that later versions do not. This was most likely a bug in particular pylint/ansible-test version. Best to not even run this one. ` Units test are run for all ansible/python version that collection is supposed to support. This should detect if we use some very recent python language feature, or import library that is not available yet in say python 3.8.
Integration tests - the PR does not yet touch them. Will be done later, I want first to get feedback on this one, and hopefully also merge it.