ansible/test
James Cammarata 188c3c608a Don't restrict local jinja2 variables to those that start with l_
Per a change in jinja2 2.9, local variables no longer are prefixed
with l_, so this updates AnsibleJ2Vars to pull in all locals (while
excluding some) regardless of name.

Fixes #20063

(cherry picked from commit 4d49b317929b86e1fc1b0cbace825ff73b372dc7)
2017-01-20 07:15:51 -06: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 Fixing iterator bug related to reworking of end-of-role detection 2017-01-19 10:10:07 -06: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.