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
Ted Timmons 5d9df86b42 Postgres ssl mode prefer (#21498)
* refactor postgres,
* adds a basic unit test module
* first step towards a common utils module
* set postgresql_db doc argument defaults to what the code actually uses

* unit tests that actually test a missing/found psycopg2, no dependency needed

* add doc fragments, use common args, ansible2ify the imports

* update dict

* add AnsibleModule import

* mv AnsibleModule import to correct file

* restore some database utils we need

* rm some more duplicated pg doc fragments

* change ssl_mode from disable to prefer, add update docs

* use LibraryError pattern for import verification

per comments on #21435. basically LibraryError and touching up its usage in pg_db and the tests.
8 years ago
..
compile refactors junos modules to support persistent socket connections (#21365) 8 years ago
integration New module: cnos_vlan and various utility files (#21107) 8 years ago
results Initial ansible-test implementation. (#18556) 8 years ago
runner network_cli shouldn't be specified anymore (#21458) 8 years ago
sanity [cloud] Ensure that s3_bucket module always enables/disables versioning if it is specified (#21320) 8 years ago
units Postgres ssl mode prefer (#21498) 8 years ago
utils Add retries to Shippable CI scripts. (#21108) 8 years ago
README.md Switch tests to pytest and ansible-test. 8 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.