ansible/test
Michael Scherer cc61531a74 Do not test vca and vmware.py for py2.4 (#15887)
Since both of them depend on libraries not
working on python 2.4, we shouldn't restrict
ourself on 2.4, cf https://github.com/ansible/ansible/pull/15870
2016-05-16 10:51:48 -04:00
..
code-smell Don't pick up whole commented lines in the urlopen code-smell tests 2016-04-22 08:24:56 -07:00
integration Run test_binary_modules 2016-05-12 12:53:44 -05:00
samples Merge branch 'samples-to-test' of https://github.com/dagwieers/ansible into dagwieers-samples-to-test 2016-05-11 09:57:21 -04:00
units Don't use 'from ansible.module_utils import foo' style here as it breaks (#15756) 2016-05-13 21:09:13 -07:00
utils Do not test vca and vmware.py for py2.4 (#15887) 2016-05-16 10:51:48 -04:00
README.md

Ansible Test System

Folders

unit

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 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.