You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ansible/test
Toshio Kuratomi 5c38f3cea2 Combine jimi-c and bcoca's ideas and work on hooking module-utils into PluginLoader.
This version just gets the relevant paths from PluginLoader and then
uses the existing imp.find_plugin() calls in the AnsiballZ code to load
the proper module_utils.

Modify PluginLoader to optionally omit subdirectories (module_utils
needs to operate on top level dirs, not on subdirs because it has
a hierarchical namespace whereas all other plugins use a flat
namespace).

Rename snippet* variables to module_utils*

Add a small number of unittests for recursive_finder

Add a larger number of integration tests to demonstrate that
module_utils is working.

Whitelist module-style shebang in test target library dirs

Prefix module_data variable with b_ to be clear that it holds bytes data
9 years ago
..
compile Ansible Tower organization module (#20355) 9 years ago
integration Combine jimi-c and bcoca's ideas and work on hooking module-utils into PluginLoader. 9 years ago
results Initial ansible-test implementation. (#18556) 9 years ago
runner Unittests for some of module_common.py (#20812) 9 years ago
sanity Combine jimi-c and bcoca's ideas and work on hooking module-utils into PluginLoader. 9 years ago
units Combine jimi-c and bcoca's ideas and work on hooking module-utils into PluginLoader. 9 years ago
utils Temporarily remove Windows Server 2016 from CI. 9 years ago
README.md Switch tests to pytest and ansible-test. 9 years ago

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.