ansible/test
Brian Coca 5e98be2e62 better handling of parsed
updated tests to match new result output
2017-03-22 12:03:43 -04:00
..
compile Remove python 2.4 compile test. 2017-03-15 15:46:12 -07:00
integration Rewrite ansible-pull tests to use local repo. (#22821) 2017-03-21 00:30:02 -07:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner Fix metadata handling for shell command. (#22801) 2017-03-20 15:31:57 -07:00
sanity E1 legacy pep8 fixes (#21933) 2017-03-21 21:19:40 -05:00
units better handling of parsed 2017-03-22 12:03:43 -04: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.