You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

James Cammarata b376e208c7 Adding "follow" param for file/copy options Also modifies the template action plugin to use this new param when executing the file/copy modules for templating so that links are preserved correctly. Fixes #8998		10 years ago
..
group_vars	First pass at ec2 module tests	11 years ago
host_vars	Adding an integration test for variable precedence	11 years ago
roles	Adding "follow" param for file/copy options	10 years ago
vars	Correct variable blending from vars_files with hostvars in them	10 years ago
Makefile	Remove galaxy CLI tests that hit bitbucket as bitbucket is hanging tests - maybe replace with nice github examples later :)	10 years ago
README.md	Add winrm integration tests for raw, script and ping modules.	11 years ago
all.yml	Add a lot of tests to verify parsing routines for scenarios that should pass. Some changes TBD, like stripping command spaces off end of expressions.	11 years ago
amazon.yml	Re-enable the ec2_eip test	10 years ago
bad_parsing.yml	Add missing file.	11 years ago
check_mode.yml	Rename tests to test, use old directory name.	11 years ago
cleanup_ec2.py	Added an integration test for the ec2_asg module	11 years ago
cleanup_gce.py	Changes cleanup_gce.py to use gce_credentials module.	11 years ago
credentials.template	Adds integration tests for gce module.	11 years ago
destructive.yml	Adding test Coverage for mysql_variable module	10 years ago
galaxy_playbook.yml	Allow installation of roles from yaml roles file	10 years ago
galaxy_roles.yml	Handle older git archive commands	10 years ago
galaxy_rolesfile	Handle older git archive commands	10 years ago
gce.yml	Adds integration tests for gce_pd module.	11 years ago
gce_credentials.py	Adds support for creating GCE persistent disks from snapshots	11 years ago
good_parsing.yml	Add a lot of tests to verify parsing routines for scenarios that should pass. Some changes TBD, like stripping command spaces off end of expressions.	11 years ago
integration_config.yml	Rename tests to test, use old directory name.	11 years ago
inventory	Test that we can override variables set in inventory when the vars_file name is templated	10 years ago
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	11 years ago
inventory.handlers	Ensure handlers run when meta tasks are defined and add handler integration tests	11 years ago
inventory.winrm.template	Add winrm integration tests for raw, script and ping modules.	11 years ago
non_destructive.yml	Fix py26 difference in ssl socket connect call from `99ba9d6`	10 years ago
rackspace.yml	Rename tests to test, use old directory name.	11 years ago
setup_gce.py	Adds support for attaching persistent disks to GCE instances	11 years ago
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	11 years ago
test_handlers.yml	Correct issue of handlers running on all hosts incorrectly	11 years ago
test_hash.yml	Rename tests to test, use old directory name.	11 years ago
test_includes.yml	Verify playbook includes can take params.	10 years ago
test_includes2.yml	Verify playbook includes can take params.	10 years ago
test_setup.yml	Rename tests to test, use old directory name.	11 years ago
test_var_precedence.yml	Test that we can override variables set in inventory when the vars_file name is templated	10 years ago
test_vault.yml	Change name of vault integration test	11 years ago
test_winrm.yml	Add integration tests for win_service module.	11 years ago
unicode.yml	Remove unnecessary unicode conversions from parse_kv	10 years ago
vars_file.yml	Rename tests to test, use old directory name.	11 years ago
vault-password	Added integration tests for encrypted vars	11 years ago

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