History

James Laska 551cb1892b Always run cleanup after running cloud_integration tests		2014-03-12 08:37:01 -04:00
..
group_vars	First pass at ec2 module tests	2014-02-26 16:43:30 -05:00
host_vars	Fix test_async by using env python	2014-03-06 13:32:05 -05:00
roles	unarchive module: Add creates functionality.	2014-03-07 18:19:46 -06:00
vars	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
all.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
amazon.yml	First pass at ec2 module tests	2014-02-26 16:43:30 -05:00
check_mode.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
cleanup_ec2.py	First pass at ec2 module tests	2014-02-26 16:43:30 -05:00
destructive.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
integration_config.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
inventory	First pass at ec2 module tests	2014-02-26 16:43:30 -05:00
Makefile	Always run cleanup after running cloud_integration tests	2014-03-12 08:37:01 -04:00
non_destructive.yml	Adding new tests for assemble role	2014-02-24 14:27:23 -06:00
rackspace.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
README.md	Update README.md	2014-02-20 19:28:06 -05:00
test_hash.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
test_setup.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -05:00
vars_file.yml	Rename tests to test, use old directory name.	2014-02-20 19:11:15 -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:

make non_destructive

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

TEST_FLAGS="--tags test_vars_blending" make

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 :)

make destructive

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.