History

James Cammarata 7a8520ac1a Fixing role dependency chain creation The dep chain for roles created during the compile step had bugs, in which the dep chain was overwriten and the original tasks in the role were not assigned a dep chain. This lead to problems in determining whether roles had already run when in a "diamond" structure, and in some cases roles were not correctly getting variables from parents. Fixes #14046		2016-01-28 15:59:43 -05:00
..
group_vars
host_vars	breaks testing in non virtual envs, since env var can be used in those	2015-11-12 09:40:43 -08:00
lookup_paths
roles	Fixing role dependency chain creation	2016-01-28 15:59:43 -05:00
vars
all.yml
amazon.yml
azure.yml
bad_parsing.yml
check_mode.yml
cleanup_azure.py
cleanup_ec2.py
cleanup_gce.py
cleanup_rax.py
cloudstack.yml
consul.yml
consul_inventory.yml
consul_running.py
credentials.template
destructive.yml	Disable docker test for Fedora, due to broken packaging	2015-12-21 10:58:49 -05:00
galaxy_playbook.yml
galaxy_playbook_git.yml	[hotfix] add missed playbook file	2016-01-26 10:45:58 -05:00
galaxy_roles.yml	Allow meta/main.yml to include roles through spec file	2015-10-22 13:30:42 +10:00
galaxy_rolesfile	Allow blank lines and comments/spaces in galaxy spec files	2015-11-04 15:36:20 +10:00
gce.yml
gce_credentials.py
good_parsing.yml
integration_config.yml
inventory
inventory.group_by
inventory.handlers
inventory.winrm.template
lookup.ini
lookup.properties
Makefile	Adding support for scm-based role source urls (incl. integration test to cover it)	2016-01-26 10:45:58 -05:00
no_log_local.yml
non_destructive.yml	fix for dynamic (add_host) hosts not available in hostvars	2015-11-16 10:53:10 -08:00
rackspace.yml
README.md
setup_gce.py
test_delegate_to.yml
test_environment.yml
test_filters.yml
test_force_handlers.yml
test_group_by.yml
test_handlers.yml
test_hash.yml
test_includes.yml
test_includes2.yml
test_lookup_properties.yml
test_setup.yml
test_tags.yml
test_templating_settings.yml
test_var_precedence.yml	reformated test, changed big assert to with_items	2015-12-01 21:26:36 -08:00
test_vault.yml
test_winrm.yml
unicode-test-script	Fix problems with non-ascii values passed as part of the command to connection plugins	2016-01-05 07:46:24 -08:00
unicode.yml	More fixes for unicode handling in the connection plugins.	2016-01-07 06:01:34 -08: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