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
Ryan Brown 2196fa0e95 [cloud][tests] fixtures for placebo to test AWS modules using boto3 (#21253) 
* [cloud][tests] Create fixtures for using placebo to test boto3-using modules

* Use pytest's importorskip instead of manually skipping on missing deps

* Fix imports in cloudformation module

* Delete unused code

* Add maybe_sleep fixtures to speed up recorded test runs

* Build basic placebo-CFN tests

* Commit placebo recordings of basic stack operations

* Add placebo to test-requires

* Allow unit tests to run regardless of environment by setting a default region

* Use explicit relative import for Python 3 compat

* Use __name__ attribute that works on Python 2 and 3
2017-03-31 15:31:12 -04:00
..
compile Remove python 2.4 compile test. 2017-03-15 15:46:12 -07:00
integration Fix eos_banner cli basic_motd integration test (#23158) 2017-03-31 00:21:23 +02:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner [cloud][tests] fixtures for placebo to test AWS modules using boto3 (#21253) 2017-03-31 15:31:12 -04:00
sanity Remove references to deleted files. 2017-03-31 09:20:15 -07:00
units [cloud][tests] fixtures for placebo to test AWS modules using boto3 (#21253) 2017-03-31 15:31:12 -04: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

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.