ansible/test
Matt Davis 73f50b4f9f fix Windows env handling (#22927)
* fixes #22441
* fixes #22655
* moves all env handling into the exec wrapper; this should work for everything but raw, which is consistent with non-Windows.
2017-03-23 17:48:15 -07:00
..
compile Remove python 2.4 compile test. 2017-03-15 15:46:12 -07:00
integration fix Windows env handling (#22927) 2017-03-23 17:48:15 -07:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner Overhaul ansible-test import analysis. (#22888) 2017-03-22 18:07:53 -07:00
sanity Update module_utils.six to latest (#22855) 2017-03-23 13:35:05 -07:00
units Update module_utils.six to latest (#22855) 2017-03-23 13:35:05 -07:00
utils Remove python2.4 package install from other test. 2017-03-15 16:40:05 -07:00
README.md Switch tests to pytest and ansible-test. 2017-01-11 12:34:59 -08:00

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.