You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ansible/test
Toshio Kuratomi 98d223a51b Facts Timeout was not settable via ansible.cfg
The timeout for gathering facts needs to be settable from three places
(highest precedence to lowest):

* programmatically
* ansible.cfg (equivalent to the user specifying it explicitly when
  calling setup)
* from the default value

The code was changed in b4bd6c80de to
allow programmatically and the default value to work correctly but
setting via ansible.cfg/parameter was broken.

This change should fix setting via ansible.cfg and adds unittests for
all three cases

Fixes #23753

(cherry picked from commit d088030fa6)
9 years ago
..
compile Use lint friendly output for python syntax checks. (#22390) 9 years ago
integration Run `save` inside config mode. (#23977) 9 years ago
results Create bot friendly sanity output. (#22381) 9 years ago
runner Fix bugs in ansible-test units command. (#24044) 9 years ago
sanity Fix bugs in ansible-test units command. (#24044) 9 years ago
units Facts Timeout was not settable via ansible.cfg 9 years ago
utils Use Shippable image: drydock/u16pytall:master 9 years ago
README.md Switch tests to pytest and ansible-test. 9 years ago

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.