History

Toshio Kuratomi f1267c0b05 Move from md5 to sha1 to work on fips-140 enabled systems		2014-11-06 21:28:04 -08:00
..
group_vars
host_vars
roles	Move from md5 to sha1 to work on fips-140 enabled systems	2014-11-06 21:28:04 -08:00
vars	Correct variable blending from vars_files with hostvars in them	2014-08-20 15:49:01 -05:00
all.yml
amazon.yml	Re-enable the ec2_eip test	2014-08-05 09:20:23 -05:00
bad_parsing.yml	Add missing file.	2014-07-23 23:32:45 -04:00
check_mode.yml
cleanup_ec2.py
cleanup_gce.py
credentials.template
destructive.yml	Adding test Coverage for mysql_variable module	2014-08-01 12:15:05 -04:00
galaxy_playbook.yml	Allow installation of roles from yaml roles file	2014-08-21 17:15:23 -04:00
galaxy_roles.yml	Allow github style ssh repo names	2014-09-10 21:55:27 +10:00
galaxy_rolesfile	Allow github style ssh repo names	2014-09-10 21:55:27 +10:00
gce.yml
gce_credentials.py
good_parsing.yml
integration_config.yml
inventory	Test that we can override variables set in inventory when the vars_file name is templated	2014-09-09 15:43:10 -07:00
inventory.group_by
inventory.handlers
inventory.winrm.template
Makefile	Fix up all python3 issues that do not have to do with text/bytes	2014-10-28 20:27:14 -04:00
non_destructive.yml	Fix bug in plugin path caching	2014-10-04 21:47:38 -05:00
rackspace.yml
README.md
setup_gce.py
test_group_by.yml	Catch template syntax errors specifically when templating strings	2014-10-20 13:11:20 -05:00
test_handlers.yml
test_hash.yml
test_includes.yml	Verify playbook includes can take params.	2014-07-26 10:41:23 -04:00
test_includes2.yml	Verify playbook includes can take params.	2014-07-26 10:41:23 -04:00
test_setup.yml
test_var_precedence.yml	Test that we can override variables set in inventory when the vars_file name is templated	2014-09-09 15:43:10 -07:00
test_vault.yml
test_winrm.yml
unicode.yml	Remove unnecessary unicode conversions from parse_kv	2014-08-04 09:59:08 -05:00
vars_file.yml
vault-password

README.md

Integration tests

The ansible integration system.

Tests for playbooks, by playbooks.

Some tests may require credentials. Credentials may be specified with credentials.yml.

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. Some tests (e.g. cloud) will only run when access credentials are provided. For more information about supported credentials, refer to credentials.template.

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

Cloud tests exercise capabilities of cloud modules (e.g. ec2_key). These are not 'tests run in the cloud' so much as tests that leverage the cloud modules and are organized by cloud provider.

In order to run cloud tests, you must provide access credentials in a file named credentials.yml. A sample credentials file named credentials.template is available for syntax help.

Provide cloud credentials: cp credentials.template credentials.yml ${EDITOR:-vi} credentials.yml

Run the tests: make cloud

WARNING running cloud integration tests will create and destroy cloud resources. Running these tests may result in additional fees associated with your cloud account. Care is taken to ensure that created resources are removed. However, it is advisable to inspect your AWS console to ensure no unexpected resources are running.

Windows Tests

These tests exercise the winrm connection plugin and Windows modules. You'll need to define an inventory with a remote Windows 2008 or 2012 Server to use for testing, and enable PowerShell Remoting to continue.

Running these tests may result in changes to your Windows host, so don't run them against a production/critical Windows environment.

Enable PowerShell Remoting (run on the Windows host via Remote Desktop): Enable-PSRemoting -Force

Define Windows inventory: cp inventory.winrm.template inventory.winrm ${EDITOR:-vi} inventory.winrm

Run the tests: make test_winrm