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 32fbd4ba24 Test the extract filter without the map filter. 
map + extract is the usual way to use it but map isn't available on
older versions of jinja2 that we still work with.  Test extract even on
those versions.
2017-01-16 13:13:34 -08:00
..
compile Initial Commit for Infinidat Ansible Modules (#19429) 2016-12-22 13:18:19 +00:00
integration Test the extract filter without the map filter. 2017-01-16 13:13:34 -08:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Clean up inventory generation in ansible-test. (#20313) 2017-01-16 12:31:17 -08:00
sanity Correct test constraints and add sanity check. 2017-01-08 16:44:31 -08:00
units adds iosxr_system declarative module (#20134) 2017-01-11 17:17:37 -05:00
utils Fix python 3.6 install. 2017-01-13 15:30:27 -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.