ansible/test
Matt Clay 36d8612ac0 Use jinja2 import instead of pip to get version.
This resolves issues with older versions of pip.

(cherry picked from commit a8fb6f0958)
2017-01-19 12:22:01 -08:00
..
code-smell Update grep for six to not falsely trigger when six is only a substring of a different library 2016-05-26 16:16:21 -07:00
integration Use jinja2 import instead of pip to get version. 2017-01-19 12:22:01 -08:00
sanity/validate-modules Backport validate-modules to stable-2.1 so we can have versioned testing (#18120) 2016-10-20 18:22:47 +01:00
units Add a test for int/float parameter type checking (#16741) 2016-09-21 20:39:02 -07:00
utils Backport validate-modules to stable-2.1 so we can have versioned testing (#18120) 2016-10-20 18:22:47 +01:00
README.md Update README.md 2015-11-03 14:11:22 -05: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.