wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ansible/test
History
Gaurav Rastogi 798972c72a Avi Networks Ansible modules. (#20415) 
* Avi Networks Ansible modules.
Avi Version: 16.3.4

* Fixed Review comments
1. Changed description to be full sentences
2. Fixed Pep8 warnings.
3. Fixed comments and descriptions.

* 1. Fixed descriptions and messages as per review comments.
2. Added descriptions for the missing parameters.

* Fixed the shippable break due to the incorrect description format

* Removed the extra modules so that there is a single module for the first commit

* Updated license to BSD based on review comments

* updated comments based on review feedback

* Refactored code to handle POST and PUT scenarios where playbook does not need to check whether object is present.
Moved ansible helper utilities to module_utils as now roles can be patched with module_utils as well.

* fixed pep8 warnings
2017-02-08 09:47:18 -05:00
..
compile Avi Networks Ansible modules. (#20415) 2017-02-08 09:47:18 -05:00
integration Set block indentation to 1 on iosxr templates (#21105) 2017-02-07 21:13:20 +01:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Add retries to Shippable CI scripts. (#21108) 2017-02-07 16:33:45 -08:00
sanity Redhat subscription (#20729) 2017-02-07 12:07:01 -05:00
units Fix vyos unit tests. 2017-02-07 15:21:34 -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.