wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ansible/test
History
John R Barker 5dac2ee00c Test eos_banner (#22201) 
* eos_banner docs improvements

* run eos_banner tests

* basic eos_banner tests

* remove trailing newlines

* remove hack

* Various eos_banner fixes

No unicode tests, as the device doesn't support it
Correctly set provider
result.command should be empty list if no changes

* test eos_banner over eapi

* revert docs changes, moved to separate PR
2017-03-10 15:20:09 +00:00
..
compile Use lint friendly output for python syntax checks. (#22390) 2017-03-07 20:27:50 -08:00
integration Test eos_banner (#22201) 2017-03-10 15:20:09 +00:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner Disable ansible color output on sanity tests. 2017-03-08 12:18:16 -08:00
sanity composer: fix escape working_dir (#22363) 2017-03-07 20:51:04 +01:00
units Fix the eos_banner idempotency (#22413) 2017-03-09 12:43:54 +00:00
utils Fix error handling in CI other script. 2017-03-08 01:31:53 -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.