e87cf4a3cc
- Add support for inserting module args into PowerShell modules. Fixes #11661. - Support Windows paths containing spaces. Applies changes from #10727 to v2. Fixes #9999. Should also fix ansible/ansible-modules-core#944 and ansible/ansible-modules-core#1007. - Change how execution policy is set for running remote scripts. Applies changes from #11092 to v2. Also fixes ansible/ansible-modules-core#1776. - Use codepage 65001 (UTF-8) for WinRM connection instead of default (CP437), convert command to UTF-8 and results from UTF-8. Replaces changes from #10024. Fixes #11198. - Close WinRM connection when task completes. - Use win_stat, win_file and win_copy modules instead of stat, file and copy when called from within other action plugins (only when using WinRM+PowerShell). - Unquote Windows path arguments before passing to win_stat, win_file, win_copy and slurp modules (only when using WinRM/PowerShell). - Check for win_ping module to determine if core modules are missing (only when using WinRM/PowerShell). - Add stdout_lines to result from running low level commands (so stdout_lines is available when using raw/script). - Update copy action plugin to use shell functions for joining paths and checking for trailing slash. - Update fetch action plugin to unquote source path when using Windows paths. - Add win_copy and win_template action plugins that inherit from copy and template. - Support running .bat and .cmd scripts using default system encoding instead of UTF-8. - Always send PowerShell commands as base64-encoded blobs to allow for running simple PowerShell commands via raw. - Support running modules on Windows with interpreters other than PowerShell. - Update integration tests to support above changes and test unicode fixes. - Add test for win_user error from ansible/ansible-modules-core#1241 (fixed by ansible/ansible-modules-core#1774). - Add test for additional win_stat output values (implemented by ansible/ansible-modules-core#1473). - Add test for OS architecture and name from setup.ps1 (implemented by ansible/ansible-modules-core#1100). All WinRM integration tests pass for me with these changes. |
9 years ago | |
|---|---|---|
| .. | ||
| group_vars | ||
| host_vars | 11 years ago | |
| roles | 9 years ago | |
| vars | 10 years ago | |
| Makefile | 9 years ago | |
| README.md | 11 years ago | |
| all.yml | 11 years ago | |
| amazon.yml | 10 years ago | |
| azure.yml | 10 years ago | |
| bad_parsing.yml | 11 years ago | |
| check_mode.yml | 10 years ago | |
| cleanup_azure.py | 10 years ago | |
| cleanup_ec2.py | 10 years ago | |
| cleanup_gce.py | 11 years ago | |
| cleanup_rax.py | 10 years ago | |
| cloudstack.yml | 10 years ago | |
| consul.yml | 10 years ago | |
| consul_inventory.yml | 10 years ago | |
| consul_running.py | 10 years ago | |
| credentials.template | 10 years ago | |
| destructive.yml | 10 years ago | |
| galaxy_playbook.yml | 10 years ago | |
| galaxy_roles.yml | 10 years ago | |
| galaxy_rolesfile | 10 years ago | |
| gce.yml | ||
| gce_credentials.py | ||
| good_parsing.yml | 11 years ago | |
| integration_config.yml | 9 years ago | |
| inventory | 10 years ago | |
| inventory.group_by | 11 years ago | |
| inventory.handlers | ||
| inventory.winrm.template | 11 years ago | |
| non_destructive.yml | 10 years ago | |
| rackspace.yml | 10 years ago | |
| setup_gce.py | 11 years ago | |
| test_delegate_to.yml | 10 years ago | |
| test_filters.yml | 10 years ago | |
| test_force_handlers.yml | 10 years ago | |
| test_group_by.yml | 10 years ago | |
| test_handlers.yml | 9 years ago | |
| test_hash.yml | ||
| test_includes.yml | 10 years ago | |
| test_includes2.yml | 10 years ago | |
| test_setup.yml | ||
| test_tags.yml | 10 years ago | |
| test_templating_settings.yml | 10 years ago | |
| test_var_precedence.yml | 10 years ago | |
| test_vault.yml | 11 years ago | |
| test_winrm.yml | 10 years ago | |
| unicode.yml | 10 years ago | |
| vars_file.yml | 10 years ago | |
| vault-password | 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