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 ed00741a01 Mcsalgado's change to use shlex.quote instead of pipes.quote (#18534) 
* Replace pipes.quote for shlex_quote

* More migration of pipes.quote to shlex_quote

Note that we cannot yet move module code over.  Modules have six-1.4
bundled which does not have shlex_quote.  This shouldn't be a problem as
the function is still importable from pipes.quote.  It's just that this
has become an implementation detail that makes us want to import from
shlex instead.

Once we get rid of the python2.4 dependency we can update to a newer
version of bundled six module-side and then we're free to use
shlex_quote everywhere.
2016-11-17 13:18:29 -08:00
..
integration Alternately track listening handlers by uuid if no name is set 2016-11-13 15:24:44 -06:00
samples Fix cosmetic problems in YAML source 2016-11-11 14:50:57 -08:00
sanity Add a check for type() instead of isinstance() (#18439) 2016-11-10 14:06:14 -08:00
units Mcsalgado's change to use shlex.quote instead of pipes.quote (#18534) 2016-11-17 13:18:29 -08:00
utils Add playbook and packer file for building httptester (#18107) 2016-11-17 17:30:30 +00:00
README.md Test reorganization and cleanup. (#18270) 2016-10-31 12:53:11 -07: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 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.