History

mikedlr 34d9415d6d [cloud][tests] AWS lambda module unit tests (#21768 ) First pass at unit tests; demonstrates no update when only one parameter changed bug that was fixed in `22701806`.		2017-02-23 09:58:26 -05:00
..
compile	refactors junos modules to support persistent socket connections (#21365 )	2017-02-16 10:53:03 -05:00
integration	Test placement (#21801 )	2017-02-22 12:43:45 -08:00
results	Initial ansible-test implementation. (#18556 )	2016-11-29 21:21:53 -08:00
runner	Pass base branch to module validator on delegate.	2017-02-20 14:28:11 -08:00
sanity	Add checks for from module_utils import * (#21800 )	2017-02-22 13:16:35 -08:00
units	[cloud][tests] AWS lambda module unit tests (#21768 )	2017-02-23 09:58:26 -05:00
utils	Restore 2008-SP2 and 2008-R2_SP1 CI testing.	2017-02-21 20:55:25 -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.