cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
ansible/test
History
stephane 77868a4104 Set Suse family for openSUSE Tumbleweed & Leap 
On openSUSE Tumbleweed, lsb-release -a currently reports
the distributor ID as "openSUSE Tumbleweed". On openSUSE
Leap, the distributor ID is "SUSE LINUX".

Add them to the OS_FAMILY dict as Suse family systems.

Also add an entry to TESTSETS in test_distribution_version.py
for openSUSE Tumbleweed.
2016-10-23 02:04:28 +02:00
..
code-smell Add a whitelist for checking for six. Use it for digital_ocean.py 2016-10-06 10:59:02 -07:00
integration tests: check that handlers are able to use 'include' 2016-10-21 20:17:42 +02:00
samples Changes to be committed: (#16430) 2016-06-24 10:26:51 -04:00
sanity/validate-modules Restore README.rst, update and fix formatting. (#18012) 2016-10-13 12:47:13 -07:00
units Set Suse family for openSUSE Tumbleweed & Leap 2016-10-23 02:04:28 +02:00
utils Enable the git test on py3 2016-10-21 09:03:35 -07:00
README.md Location of Network Tests (#18048) 2016-10-16 11:01:04 +01:00

README.md

Ansible Test System

Folders

unit

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.

Tests for network modules can be found in https://github.com/ansible/test-network-modules/

learn more

hop into a subdirectory and see the associated README.md for more info.