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.
ansible/test/integration
Toshio Kuratomi 67ff4428d5 Fix up all python3 issues that do not have to do with text/bytes 10 years ago
..
group_vars
host_vars
roles Remove test case that wasn't reported as something git should do 10 years ago
vars
Makefile Fix up all python3 issues that do not have to do with text/bytes 10 years ago
README.md Add winrm integration tests for raw, script and ping modules. 11 years ago
all.yml
amazon.yml
bad_parsing.yml
check_mode.yml
cleanup_ec2.py
cleanup_gce.py
credentials.template Adds integration tests for gce module. 11 years ago
destructive.yml
galaxy_playbook.yml Allow installation of roles from yaml roles file 10 years ago
galaxy_roles.yml Allow github style ssh repo names 10 years ago
galaxy_rolesfile Allow github style ssh repo names 10 years ago
gce.yml
gce_credentials.py Adds support for creating GCE persistent disks from snapshots 11 years ago
good_parsing.yml
integration_config.yml
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
inventory.winrm.template
non_destructive.yml Fix bug in plugin path caching 10 years ago
rackspace.yml Rename tests to test, use old directory name. 11 years ago
setup_gce.py
test_group_by.yml Catch template syntax errors specifically when templating strings 10 years ago
test_handlers.yml
test_hash.yml
test_includes.yml Verify playbook includes can take params. 10 years ago
test_includes2.yml
test_setup.yml
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
test_winrm.yml
unicode.yml
vars_file.yml Rename tests to test, use old directory name. 11 years ago
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