mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00

History

Michael DeHaan 13076ca8be Remove stray shell script.		2014-02-20 13:04:24 -05:00
..
roles	Add changed_when test	2014-02-20 12:45:56 -05:00
all.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
amazon.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
destructive.yml	Adding new test role for the service module	2014-02-19 18:06:46 -05:00
integration_config.yml	Add a partial test of variable blending to the test infrastructure.	2014-02-20 12:52:17 -05:00
inventory	Add a partial test of variable blending to the test infrastructure.	2014-02-20 12:52:17 -05:00
Makefile	Convert test system to use Make	2014-02-20 13:00:05 -05:00
non_destructive.yml	Add a partial test of variable blending to the test infrastructure.	2014-02-20 12:52:17 -05:00
rackspace.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00
README.md	Convert test system to use Make	2014-02-20 13:00:05 -05:00
test_setup.yml	Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier.	2014-02-13 18:28:29 -05:00

README.md

Integration tests

The ansible integration system.

Tests for playbooks, by playbooks.

Some tests may require cloud credentials.

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.

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

Details pending, but these require cloud credentials. These are not 'tests run in the cloud' so much as tests that leverage the cloud modules and are organized by cloud provider.

Instructions

Pending