ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity
community.general/test
History
Will Thames 103ede26df Ensure ssh hostkey checks respect server port (#20840) 
* Add tests for `get_fqdn_and_port` method.

Currently tests verify original behavior - returning default `ssh-keyscan` port
Add test around `add_host_key` to verify underlying command arguments
Add some new expectations for `get_fqdn_and_port`
Test that non-standard port is passed to `ssh-keyscan` command

* Ensure ssh hostkey checks respect server port

ssh-keyscan will default to getting the host key for port 22.
If the ssh service is running on a different port, ssh-keyscan
will need to know this.

Tidy up minor flake8 issues

* Update known_hosts tests for port being None

Ensure that git urls don't try and set port when a path
is specified

Update known_hosts tests to meet flake8

* Fix stdin swap context for test_known_hosts

Move test_known_hosts from under basic, as it is its own library.
Remove module_utils.known_hosts from pep8 legacy files list
2017-02-15 11:47:57 -08:00
..
compile Change the f5 modules to use f5_utils file (#21466) 2017-02-15 16:51:13 +00:00
integration Test the slurp module 2017-02-15 11:14:03 -08:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner network_cli shouldn't be specified anymore (#21458) 2017-02-15 12:58:12 +00:00
sanity Ensure ssh hostkey checks respect server port (#20840) 2017-02-15 11:47:57 -08:00
units Ensure ssh hostkey checks respect server port (#20840) 2017-02-15 11:47:57 -08: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.