ansible/test
John R Barker 5b4ea08a1f Formatting (#18260)
* Formatting

* Update README.md

* Update
2016-10-31 14:07:51 +00:00
..
code-smell Add a whitelist for checking for six. Use it for digital_ocean.py 2016-10-06 10:59:02 -07:00
integration Formatting (#18260) 2016-10-31 14:07:51 +00:00
samples Changes to be committed: (#16430) 2016-06-24 10:26:51 -04:00
sanity/validate-modules Restore README.rst, update and fix formatting. (#18012) 2016-10-13 12:47:13 -07:00
units Change v2_playbook_on_start logic to positively detect legacy plugins 2016-10-28 10:05:58 -07:00
utils Enable the git test on py3 2016-10-21 09:03:35 -07:00
README.md Migrate Network Tests into ansible/ansible (#18233) 2016-10-28 19:50:29 +01:00

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.