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 4b0aa1214c Ziploader
* Ziploader proof of concept (jimi-c)

* Cleanups to proof of concept ziploader branch:

* python3 compatible base64 encoding
* zipfile compression (still need to enable toggling this off for
  systems without zlib support in python)
* Allow non-wildcard imports (still need to make this recusrsive so that
  we can have module_utils code that imports other module_utils code.)
* Better tracebacks: module filename is kept and module_utils directory
  is kept so that tracebacks show the real filenames that the errors
  appear in.

* Make sure we import modules that are used into the module_utils files that they are used in.

* Set ansible version in a more pythonic way for ziploader than we were doing in module replacer

* Make it possible to set the module compression as an inventory var

This may be necessary on systems where python has been compiled without
zlib compression.

* Refactoring of module_common code:

* module replacer only replaces values that make sense for that type of
  file (example: don't attempt to replace python imports if we're in
  a powershell module).
* Implement configurable shebang support for ziploader wrapper
* Implement client-side constants (for SELINUX_SPECIAL_FS and SYSLOG)
  via environment variable.
* Remove strip_comments param as we're never going to use it (ruins line
  numbering)

* Don't repeat ourselves about detecting REPLACER

* Add an easy way to debug

* Port test-module to the ziploader-aware modify_module()

* strip comments and blank lines from the wrapper so we send less over the wire.

* Comments cleanup

* Remember to output write the module line itself in powershell modules

* for line in lines strips the newlines so we have to add them back in
9 years ago
..
group_vars
host_vars
lookup_paths
roles Ziploader 9 years ago
test_blocks Fixing PlayIterator bugs 9 years ago
vars
Makefile Merge pull request #15207 from mattclay/verbose-test 9 years ago
README.md
all.yml
amazon.yml
azure.yml
bad_parsing.yml
check_mode.yml
cleanup_azure.py
cleanup_ec2.py
cleanup_gce.py
cleanup_rax.py
cloudflare.yml Add integration tests for the cloudflare_dns module 9 years ago
cloudstack.yml cloudstack: new integration tests test_cs_resourcelimit 9 years ago
consul.yml
consul_inventory.yml
consul_running.py
credentials.template Add integration tests for the cloudflare_dns module 9 years ago
destructive.yml Integration tests for zypper repository 9 years ago
galaxy_playbook.yml
galaxy_playbook_git.yml [hotfix] add missed playbook file 9 years ago
galaxy_roles.yml Add tests for #10620 9 years ago
galaxy_rolesfile Add tests for #10620 9 years ago
gce.yml
gce_credentials.py
good_parsing.yml
integration_config.yml
inventory add a fact gathering check for the default of all 9 years ago
inventory.group_by
inventory.handlers
inventory.local re-integrate test_test_infra output checking 9 years ago
inventory.winrm.template Add connection tests for winrm connection plugin. 9 years ago
lookup.ini
lookup.properties
no_log_local.yml
non_destructive.yml
rackspace.yml
setup_gce.py
test_connection.inventory Run more connection tests in Docker. 9 years ago
test_connection.yml Add unicode dir to connection tests. 9 years ago
test_connection_winrm.yml Add connection tests for winrm connection plugin. 9 years ago
test_delegate_to.yml
test_environment.yml
test_filters.yml
test_force_handlers.yml
test_gathering_facts.yml Make the fact gathering give a little more information on failure 9 years ago
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_test_infra.yml improve test_test_infra debug messaging, rc check 9 years ago
test_var_precedence.yml reformated test, changed big assert to with_items 9 years ago
test_vault.yml
test_winrm.yml adding integration tests for win_regmerge module (extras) 9 years ago
unicode-test-script Fix problems with non-ascii values passed as part of the command to connection plugins 9 years ago
unicode.yml More fixes for unicode handling in the connection plugins. 9 years ago
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