ansible/test
James Cammarata ca5b361ad8 Reworking iterator logic regarding failed states during always
Previous changes addressed a corner case, which unfortunately introduced
another bug. This patch adds a new flag to the host state (did_rescue) which
is set to true when the rescue portion of a block completes. This flag is
then checked in _check_failed_state() when the fail_state != FAILED_NONE.

This lead to the discovery of another bug - current strategies are not advancing
hosts to ITERATING_COMPLETE after doing a peek at the next task, leaving the
host state in the run_state of the final task. To address this, before gathering
the list of failed hosts in StrategyBase.run(), a final pass through the iterator
for all hosts is done to ensure each host is in its final state. This way, no
strategy derived from StrategyBase has to worry about it and it's handled.

Fixes #17983
2016-11-16 10:21:46 -06:00
..
integration Alternately track listening handlers by uuid if no name is set 2016-11-13 15:24:44 -06:00
samples Fix cosmetic problems in YAML source 2016-11-11 14:50:57 -08:00
sanity Add a check for type() instead of isinstance() (#18439) 2016-11-10 14:06:14 -08:00
units Reworking iterator logic regarding failed states during always 2016-11-16 10:21:46 -06:00
utils Lint YAML files under test/ 2016-11-11 14:50:57 -08:00
README.md Test reorganization and cleanup. (#18270) 2016-10-31 12:53:11 -07: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 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.