History

James Tanner d11d9fd66c Add synchronize test		2014-02-19 17:32:37 -05:00
..
roles	Add synchronize test	2014-02-19 17:32:37 -05:00
all.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
amazon.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
destructive.yml	Fix gem role ref	2014-02-19 15:59:50 -05:00
integration_config.yml	Update README.	2014-02-19 15:36:51 -05:00
inventory	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
non_destructive.yml	Add synchronize test	2014-02-19 17:32:37 -05:00
rackspace.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
README.md	Add a note about test prereqs	2014-02-19 16:44:54 -05:00
test.sh	Take inputs from config file.	2014-02-19 14:39:47 -05:00
test_destructive.sh	Add ruby gem test	2014-02-19 15:59:25 -05:00
test_setup.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00

README.md

Integration tests

The ansible integration system.

Tests for playbooks, by playbooks.

Some tests may require cloud credentials.

Tests should be run as root.

Configuration

Making your own version of integration_config.yml can allow for setting some tunable parameters to help run the tests better in your environment.

Prerequisites

The tests will assume things like hg, svn, and git are installed and in path.

(Complete list pending)

Non-destructive Tests

These tests will modify files in subdirectories, but will not do things that install or remove packages or things outside of those test subdirectories. They will also not reconfigure or bounce system services.

Run as follows:

# sh test.sh # OR
# ansible-playbook non_destructive.yml -i inventory -e @integration_config.yml -v $*

You can select specific tests with the --tags parameter.

Destructive Tests

These tests are allowed to install and remove some trivial packages. You will likely want to devote these to a virtual environment. They won't reformat your filesystem, however :)

# ansible-playbook destructive.yml -i inventory -e @integration_config.yml -v $*

Cloud Tests

Details pending, but these require cloud credentials. These are not 'tests run in the cloud' so much as tests that leverage the cloud modules and are organized by cloud provider.

Instructions

Pending