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
Matt Clay d66ce40ecb Overhaul ansible-test sanity implementation. (#22177) 
- Tests are run to completion instead of stopping on first failure.
- Test results are now parsed instead of passing through to the console.
- Test results can be saved in junit xml format.
- Test results will show up on the Shippable "Tests" result tab.
- Added an experimental --lint option for easier integration with other tools.
- Code smell tests are now usable with the --list-tests, --test and --skip-test options.
- Code split out from executor.py into sanity.py.
- Rename download-logs to download.py and add support for test and coverage results.
- Miscellaneous improvements.
2017-03-02 12:36:46 -08:00
..
compile Renamed the avi_ansible_utils to avi. Fixed the import error and clea… (#22112) 2017-03-01 16:16:59 +00:00
integration New module: cnos_vlag (#21535) 2017-03-02 16:11:37 +00:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Overhaul ansible-test sanity implementation. (#22177) 2017-03-02 12:36:46 -08:00
sanity Overhaul ansible-test sanity implementation. (#22177) 2017-03-02 12:36:46 -08:00
units [cloud] bugfix for lambda module with empty environment (#22196) 2017-03-02 09:25:39 -05:00
utils Overhaul ansible-test sanity implementation. (#22177) 2017-03-02 12:36:46 -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.