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
s-hertel 65815c3875 Refactoring Galaxy unit tests for uniformity (#20828) 
* Making tests more uniform

Removing unnecessary GalaxyCLI arguments/patching of the command line since parsing of the CLI args has been modified.

Run GalaxyCLI.parse() without saving the returned value to be uniform with the rest of the code.

Fix test_execute_remove to use the correct path

Use GalaxyCLI.run() instead of super(GalaxyCLI, gc).run() and GalaxyCLI.api = ansible.galaxy.api.GalaxyAPI(gc.galaxy).

* Refactor so one unit test checks one thing instead of multiple.

Improve readability by using a dict instead of lots of elifs

* Removing import used for debugging

* Fixing PEP 8 issues.

* Fix PEP 8 issues
2017-02-08 16:35:06 -05:00
..
compile Avi Networks Ansible modules. (#20415) 2017-02-08 09:47:18 -05:00
integration known_hosts: support --diff (#20349) 2017-02-08 09:56:03 -05:00
results Initial ansible-test implementation. (#18556) 2016-11-29 21:21:53 -08:00
runner Add retries to Shippable CI scripts. (#21108) 2017-02-07 16:33:45 -08:00
sanity Fix type() usage check in validate-modules. 2017-02-08 12:17:10 -08:00
units Refactoring Galaxy unit tests for uniformity (#20828) 2017-02-08 16:35:06 -05:00
utils Add retries to Shippable CI scripts. (#21108) 2017-02-07 16:33:45 -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.