cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
ansible/test
History
Toshio Kuratomi 1609afbd12 Unittests for some of module_common.py (#20812) 
* Unittests for some of module_common.py
* Port test_run_command to use pytest-mock

The use of addCleanup(patch.stopall) from the unittest idiom was
conflicting with the pytest-mock idiom of closing all patches
automatically.  Switching to pytest-mock ensures that the patches are
closed and removing the stopall stops the conflict.
2017-01-30 13:51:27 -08:00
..
compile Ansible Tower organization module (#20355) 2017-01-30 13:42:32 -05:00
integration PEP 8 whitespace cleanup. (#20783) 2017-01-27 15:45:23 -08:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Unittests for some of module_common.py (#20812) 2017-01-30 13:51:27 -08:00
sanity PEP 8 indent cleanup. (#20800) 2017-01-29 07:28:53 +00:00
units Unittests for some of module_common.py (#20812) 2017-01-30 13:51:27 -08:00
utils Temporarily remove Windows Server 2016 from CI. 2017-01-27 11:56:50 -08:00
README.md Switch tests to pytest and ansible-test. 2017-01-11 12:34:59 -08:00

README.md

Ansible Test System

Folders

units

Unit tests that test small pieces of code not suited for the integration test layer, usually very API based, and should leverage mock interfaces rather than producing side effects.

Playbook engine code is better suited for integration tests.

Requirements: sudo pip install paramiko PyYAML jinja2 httplib2 passlib nose pytest mock

integration

Integration test layer, constructed using playbooks.

Some tests may require cloud credentials, others will not, and destructive tests are separated from non-destructive so a subset can be run on development machines.

learn more

hop into a subdirectory and see the associated README.md for more info.