cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
ansible/test
History
Peter Sprygada dc23667cc2 add back reverted change to network_cli (#18761) 
This adds back the change to the network_cli plugin.  Ths change adds
the ensure_connect decorator to the open_shell() method to make sure
the connection is valid before trying to open a shell.

The issue was due to the addition of the decorator that will call
_connect() when there is no connection.  The _connect() method should
have been mocked in the test case.  This commit fixes the test
case as well

Change was originally reverted in c414ded69a
2016-12-05 21:42:09 -05:00
..
compile Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
integration vyos: Don't run show commands that are over ANSIBLE_VYOS_TERMINAL_LENGTH (#18682) 2016-11-30 17:08:52 +00:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Correct change classification for network plugins. 2016-12-05 20:07:18 -05:00
samples Fix cosmetic problems in YAML source 2016-11-11 14:50:57 -08:00
sanity Add unify_repos.sh to shellcheck skip list. 2016-11-30 23:44:17 -08:00
units add back reverted change to network_cli (#18761) 2016-12-05 21:42:09 -05:00
utils Update coverage exclusions. (#18675) 2016-11-29 22:46:56 -08:00
README.md Test reorganization and cleanup. (#18270) 2016-10-31 12:53:11 -07:00

README.md

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.