ansible/test
Toshio Kuratomi 78ced5318f Fix for recursive copy slowness
Copy module was walking over files in subdirectories repeatedly (a
directory tree a few levels deep could bring the time spent into the
tens of minutes)

This was traced to the fix for this bug report: https://github.com/ansible/ansible/issues/13013

Fixed #13013 a different way and added an integration test to check for
regressions of #13013 as we optimize this code.

Fixes #21513
2017-04-07 12:41:42 -04:00
..
compile Remove python 2.4 compile test. 2017-03-15 15:46:12 -07:00
integration Fix for recursive copy slowness 2017-04-07 12:41:42 -04:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner Initial pylint support for ansible-test sanity. 2017-04-04 16:16:21 -07:00
sanity Fix errors reported by pylint. (#23282) 2017-04-06 16:58:16 -07:00
units Ignores ControlPersist broken pipe errors. Fixes #16731 2017-04-07 09:06:28 -07:00
utils Update fedora24 Dockerfile to resolve dnf issue. 2017-04-06 16:03:29 -07:00
README.md Update unit test requirements in README. 2017-04-04 10:55:49 -07: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: pip install -r test/runner/requirements/units.txt

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.