History

Marius Gedminas 2efb692cc4 known_hosts: support --diff (#20349 ) * known_hosts: support --diff * known_hosts: support --diff also without --check * Add unit tests and fix incorrect diff in one corner case Tests are good! * Refactor for readability * Python 3 compat * More Python 3 compat * Add an integration test for known_hosts * Handle ssh-keygen -HF returning non-zero exit code AFAICT this is a bug in ssh-keygen in some newer OpenSSH versions (>= 6.4 probably; see commit `dd9d5cc670`): when you invoke ssh-keygen with -H and -F <host> options, it always returns exit code 1. This is because in ssh-keygen.c there's a function do_known_hosts() which calls exit (find_host && !ctx.found_key); at the end, and find_host is 1 (because we passed -F on the command line), but ctx.found_key is always 0. Why is found_key always 0? Because the callback passed to hostkeys_foreach(), which is known_hosts_hash(), never bothers to set found_key to 1. * This test does not need root * Avoid ssh-ed25519 keys in sample known_hosts file Older versions of OpenSSH do not like them and ssh-keygen -HF aborts with an error when it sees such keys: line 5 invalid key: example.net... /root/ansible_testing/known_hosts is not a valid known_hosts file. * Fix Python 3 errors Specifically, the default mode of tempfile.NamedTemporaryFile is 'w+b', which means Python 3 wants us to write bytes objects to it -- but the keys we have are all unicode strings.		2017-02-08 09:56:03 -05:00
..
compile	Avi Networks Ansible modules. (#20415 )	2017-02-08 09:47:18 -05:00
integration	known_hosts: support --diff (#20349 )	2017-02-08 09:56:03 -05:00
results
runner	Add retries to Shippable CI scripts. (#21108 )	2017-02-07 16:33:45 -08:00
sanity	Redhat subscription (#20729 )	2017-02-07 12:07:01 -05:00
units	known_hosts: support --diff (#20349 )	2017-02-08 09:56:03 -05:00
utils	Add retries to Shippable CI scripts. (#21108 )	2017-02-07 16:33:45 -08:00
README.md	Switch tests to pytest and ansible-test.	2017-01-11 12:34:59 -08: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 pytest 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.