History

Chris Church 5b85252043 Add tests for windows setup module.		2014-06-19 14:26:42 -05:00
..
group_vars
host_vars	Adding an integration test for variable precedence	2014-05-09 11:42:57 -05:00
roles	Add tests for windows setup module.	2014-06-19 14:26:42 -05:00
vars	Added integration tests for encrypted vars	2014-05-21 21:06:47 +02:00
all.yml
amazon.yml	Added an integration test for the ec2_asg module	2014-06-05 16:18:31 -05:00
check_mode.yml
cleanup_ec2.py	Added an integration test for the ec2_asg module	2014-06-05 16:18:31 -05:00
credentials.template
destructive.yml
integration_config.yml
inventory	Adding an integration test for the ec2_elb module	2014-04-28 20:37:08 -05:00
inventory.group_by	Add integration tests for group_by module. Fixed bug introduced by ansible/ansible#7273 while also fixing issue described in ansible/ansible#6953	2014-05-06 22:30:37 -04:00
inventory.handlers
inventory.winrm.template	Add winrm integration tests for raw, script and ping modules.	2014-06-19 14:24:13 -05:00
Makefile	Add winrm integration tests for raw, script and ping modules.	2014-06-19 14:24:13 -05:00
non_destructive.yml	Fixing some parsing issues in authorized_key module	2014-04-02 15:02:54 -05:00
rackspace.yml
README.md	Add winrm integration tests for raw, script and ping modules.	2014-06-19 14:24:13 -05:00
test_group_by.yml	Add integration tests for group_by module. Fixed bug introduced by ansible/ansible#7273 while also fixing issue described in ansible/ansible#6953	2014-05-06 22:30:37 -04:00
test_handlers.yml	Correct issue of handlers running on all hosts incorrectly	2014-05-27 12:03:08 -05:00
test_hash.yml
test_setup.yml
test_var_precedence.yml	Adding an integration test for variable precedence	2014-05-09 11:42:57 -05:00
test_vault.yml	Change name of vault integration test	2014-06-10 10:07:50 -05:00
test_winrm.yml	Add tests for windows setup module.	2014-06-19 14:26:42 -05:00
vars_file.yml
vault-password	Added integration tests for encrypted vars	2014-05-21 21:06:47 +02:00

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