cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
ansible/test
History
James Cammarata c669a381d1 Don't immediately return failed for any_errors_fatal tasks 
Instead of immediately returning a failed code (indicating a break in
the play execution), we internally 'or' that failure code with the result
(now an integer flag instead of a boolean) so that we can properly handle
the rescue/always portions of blocks and still remember that the break
condition was hit.

Fixes #16937
2016-08-12 14:18:50 -05:00
..
code-smell Port urls.py to python3 and other byte vs text fixes (#16124) 2016-06-04 16:19:57 -07:00
integration Cache tasks by uuid in PlayIterator for O(1) lookups 2016-08-10 12:49:19 -05:00
samples Changes to be committed: (#16430) 2016-06-24 10:26:51 -04:00
units Don't immediately return failed for any_errors_fatal tasks 2016-08-12 14:18:50 -05:00
utils Update ansible-core-ci endpoint. (#17071) 2016-08-12 12:07:41 -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.