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
Toshio Kuratomi d1a6b07fe1 Move ssh and local connection plugins from using raw select to selectors 
At the moment, this change will use EPoll on Linux, KQueue on *BSDs,
etc, so it should alleviate problems with too many open file
descriptors.

* Bundle a copy of selectors2 so that we have the selectors API everywhere.
* Add licensing information to selectors2 file so it's clear what the
  licensing terms and conditions are.
* Exclude the bundled copy of selectors2 from our boilerplate code-smell test
* Rewrite ssh_run tests to attempt to work around problem with mocking
  select on shippable

Fixes #14143
2017-02-03 08:23:50 -08:00
..
compile Ansible Tower organization module (#20355) 2017-01-30 13:42:32 -05:00
integration Fix 'touch' mode so it creates zero size files. (#20876) 2017-02-03 13:36:47 +01:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Add --debug option to ansible-test. 2017-02-01 16:05:03 -08:00
sanity Move ssh and local connection plugins from using raw select to selectors 2017-02-03 08:23:50 -08:00
units Move ssh and local connection plugins from using raw select to selectors 2017-02-03 08:23:50 -08:00
utils Temporarily remove Windows Server 2016 from CI. 2017-01-27 11:56:50 -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.