ansible/test
James Cammarata fbec2d9692 Expand return code values returned by TQM and strategies
This allows the PlaybookExecutor to receive more information regarding
what happened internal to the TaskQueueManager and strategy, to determine
things like whether or not the play iteration should stop.

Fixes #15523
2016-06-08 10:21:57 -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 Split integration tests into multiple groups. 2016-06-04 12:02:11 -07:00
samples Merge branch 'samples-to-test' of https://github.com/dagwieers/ansible into dagwieers-samples-to-test 2016-05-11 09:57:21 -04:00
units Expand return code values returned by TQM and strategies 2016-06-08 10:21:57 -05:00
utils Detect use of Travis tests on Shippable. 2016-06-06 13:36:21 -07: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.