wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ansible/test
History
Dag Wieers ac43a1bbbc Windows: Use the correct newline sequence for the platform (#21846) 
This change to the template action plugin make template use the
platform's native newline_sequence for Jinja.

We also added the option `newline_sequence` to change the newline
sequence using by Jinja if you need to use another newline sequence than
the platform default.

This was previously discussed in
https://github.com/ansible/ansible/issues/16255#issuecomment-278289414

And also relates to issue #21128
2017-03-23 19:47:10 -07:00
..
compile Remove python 2.4 compile test. 2017-03-15 15:46:12 -07:00
integration Windows: Use the correct newline sequence for the platform (#21846) 2017-03-23 19:47:10 -07:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner Overhaul ansible-test import analysis. (#22888) 2017-03-22 18:07:53 -07:00
sanity Windows: Use the correct newline sequence for the platform (#21846) 2017-03-23 19:47:10 -07:00
units Update module_utils.six to latest (#22855) 2017-03-23 13:35:05 -07:00
utils Remove python2.4 package install from other test. 2017-03-15 16:40:05 -07: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.