ansible/test
John R Barker 7330ab8062 Correctly call get_config (#20452)
* Correctly call get_config

* remove debug

* Check for empty flags and LocalAnsibleModule

* Peter's feedback
2017-01-20 20:17:35 +00:00
..
compile Initial Commit for Infinidat Ansible Modules (#19429) 2016-12-22 13:18:19 +00:00
integration Don't restrict local jinja2 variables to those that start with l_ 2017-01-20 07:15:51 -06:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Enable Windows 2016 on Shippable. 2017-01-18 18:37:42 -08:00
sanity Correct test constraints and add sanity check. 2017-01-08 16:44:31 -08:00
units Correctly call get_config (#20452) 2017-01-20 20:17:35 +00:00
utils Enable Windows 2016 on Shippable. 2017-01-18 18:37:42 -08: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.