ansible/test/integration
2015-03-11 20:58:21 -07:00
..
group_vars
host_vars
roles preliminary privlege escalation unification + pbrun 2015-03-10 18:42:36 -04: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
check_mode.yml Rework the shell quoting of remote checksumming 2015-03-02 15:42:18 -08:00
cleanup_ec2.py
cleanup_gce.py
cleanup_rax.py Don't hardcode list of delete functions to loop through 2015-02-11 12:59:02 -06:00
consul.yml Initial commit of Ansible support for the Consul clustering framework (http://consul.io). 2015-01-24 01:09:03 +00:00
consul_inventory.yml Initial commit of Ansible support for the Consul clustering framework (http://consul.io). 2015-01-24 01:09:03 +00:00
consul_running.py Initial commit of Ansible support for the Consul clustering framework (http://consul.io). 2015-01-24 01:09:03 +00:00
credentials.template Add integration tests for the rax module 2015-01-09 15:08:58 -06:00
destructive.yml preliminary privlege escalation unification + pbrun 2015-03-10 18:42:36 -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 Adding first pass at win_copy, win_file and win_template modules. 2014-12-16 04:47:01 +00:00
inventory Test case for #10426 2015-03-11 20:58:21 -07:00
inventory.group_by
inventory.handlers
inventory.winrm.template
Makefile fix tag test that broke with new tag info displayed in list tasks 2015-03-11 16:28:37 -04:00
non_destructive.yml New test that binary contenti. 2014-12-10 11:37:32 -08:00
rackspace.yml Add tests for rax_cdb_database 2015-02-11 12:59:02 -06:00
README.md
setup_gce.py
test_delegate_to.yml Fix remote_checksum with delegate_to and add tests for several ways that delegate_to works 2014-12-08 12:44:44 -08:00
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_tags.yml added tests 2015-02-13 08:27:07 -05:00
test_templating_settings.yml Proper git commit of the new integration test 2015-02-26 14:53:51 -08:00
test_var_precedence.yml Integration tests for #9242 and #9640 2014-11-26 10:55:37 -08:00
test_vault.yml
test_winrm.yml Adding first pass at win_copy, win_file and win_template modules. 2014-12-16 04:47:01 +00:00
unicode.yml Test case for #10426 2015-03-11 20:58:21 -07:00
vars_file.yml added tests for templating and with_items 2014-12-09 11:31:21 -05:00
vault-password

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