1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
community.general/test
Miyurz 1ea1becf23 Fixes bug https://github.com/ansible/ansible/issues/22455 - Git reset… (#22502)
* Fixes bug https://github.com/ansible/ansible/issues/22455 - Git reset fails when file with the name 'origin' is present in the repository

* #22455 Integration test for git module to test if it clones a repository with a file named origin

* Fixed yaml errors for test/integration/roles/test_git_clone/tasks/main.yml

* Removed the newly added target git and moved the code to test/integration/targets/git

* Reorganised code structure as per comments

* Fixed playbook name

* Added code that didn't make it to the playbook before.

* No longer need git.yml

* Remove non tasks specific code from tasks file and use existing variables

* Removed msg var from the vars.yml
2017-03-28 08:41:25 -04:00
..
compile Remove python 2.4 compile test. 2017-03-15 15:46:12 -07:00
integration Fixes bug https://github.com/ansible/ansible/issues/22455 - Git reset… (#22502) 2017-03-28 08:41:25 -04: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 Ansible 2.3 feature support for dellos9 and dellos10 (#22856) 2017-03-27 19:32:57 +01:00
units Update module_utils.six to latest (#22855) 2017-03-23 13:35:05 -07:00
utils Update Shippable downloader to support new API. 2017-03-24 14:24:38 -07:00
README.md Switch tests to pytest and ansible-test. 2017-01-11 12:34:59 -08:00

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.