ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-22 20:13:59 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
community.general/test
History
Dusty Mabe b817f1f3ea actions/unarchive: fix unarchive from remote url (#17126) 
* actions/unarchive: fix unarchive from remote url

Currently unarchive from remote url does not work because the core
unarchive module was updated to support 'remote_src' [1], but the
unarchive action plugin was not updated for this. This causes failures
because the action plugin assumes it needs to copy a file to the
remote server, but in the case of downloading a file from a remote
url a local file does not exist, so an error occurs when the file is
not found.

[1] 467516e

* test_unarchive: fix test with wrong remote_src use

The non-ascii filenames test had improperly set remote_src=yes even
though it was actually copying the file from the local machine (i.e.
the file did not already exist remotely). This test was passing
until the remote_src behavior of unarchive was fixed in 276550f.
2016-08-19 08:16:21 -05:00
..
code-smell Port urls.py to python3 and other byte vs text fixes (#16124) 2016-06-04 16:19:57 -07:00
integration actions/unarchive: fix unarchive from remote url (#17126) 2016-08-19 08:16:21 -05:00
samples Changes to be committed: (#16430) 2016-06-24 10:26:51 -04:00
units Fix facts.py for python3 (#17131) 2016-08-18 09:36:03 -04:00
utils moved from extras repo where it incorrectly exists (#17124) 2016-08-18 09:47:21 -04:00
README.md Update README.md 2015-11-03 14:11:22 -05:00

README.md

Ansible Test System

Folders

unit

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.