wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ansible/test
History
Abhijit Menon-Sen cc71765d9e Use loop_control.loop_var directly 
6eefc11c converted task.loop_control into an object, but while the other
callers were updated to use .loop_var instead of .get('loop_var'), this
site was overlooked.

This can be reproduced by including with loop_control a file that does
set_fact; a simple regression test along these lines is included.

(cherry picked from commit 950cc26aab)
2016-09-23 10:39:06 -05: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 loop_control.loop_var directly 2016-09-23 10:39:06 -05:00
units Add a test for int/float parameter type checking (#16741) 2016-09-21 20:39:02 -07:00
utils Update shippable shared dir for COPY_SOURCE. (#16511) 2016-06-29 15:11:32 -07:00
README.md Update README.md 2015-11-03 14:11:22 -05: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.