Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/ansible/tox-ansible

The tox-ansible plugin dynamically creates a full matrix of python interpreter and ansible-core version environments for running integration, sanity, and unit for an ansible collection both locally and in a Github action. tox virtual environments are leveraged for collection building, collection installation, dependency installation, and testing.
https://github.com/ansible/tox-ansible

ansible ansible-dev-tools ansible-devtools molecule molecule-plugin tox-environment tox-plugin

Last synced: about 20 hours ago
JSON representation

The tox-ansible plugin dynamically creates a full matrix of python interpreter and ansible-core version environments for running integration, sanity, and unit for an ansible collection both locally and in a Github action. tox virtual environments are leveraged for collection building, collection installation, dependency installation, and testing.

Awesome Lists containing this project

README 

        
# tox-ansible



## Introduction



`tox-ansible` is a utility designed to simplify the testing of Ansible content collections.



Implemented as a `tox` plugin, `tox-ansible` provides a simple way to test Ansible content collections across multiple Python interpreters and Ansible versions.



`tox-ansible` uses familiar python testing tools to perform the actual testing. It uses `tox` to create and manage the testing environments, `ansible-test sanity` to run the sanity tests, and `pytest` to run the unit and integration tests. This eliminated the black box nature of other approaches and allowed for more control over the testing process.



When used on a local development system, each of the environments are left intact after a test run. This allows for easy debugging of failed tests for a given test type, python interpreter and Ansible version.



By using `tox` to create and manage the testing environments, Test outcomes should always be the same on a local development system as they are in a CI/CD pipeline.



`tox` virtual environments are created in the `.tox` directory. These are easily deleted and recreated if needed.



## Talk to us



Need help or want to discuss the project? See our [Contributor guide](https://ansible.readthedocs.io/projects/tox-ansible/contributor_guide/#talk-to-us) join the conversation!



## Installation



Install from pypi:



```bash

pip install tox-ansible

```



## Usage



From the root of your collection, create an empty `tox-ansible.ini` file and list the available environments:



```bash

touch tox-ansible.ini

tox list --ansible --conf tox-ansible.ini

```



A list of dynamically generated Ansible environments will be displayed:



```



default environments:

...

integration-py3.11-2.14      -> Integration tests for ansible.scm using ansible-core 2.14 and python 3.11

integration-py3.11-devel     -> Integration tests for ansible.scm using ansible-core devel and python 3.11

integration-py3.11-milestone -> Integration tests for ansible.scm using ansible-core milestone and python 3.11

...

sanity-py3.11-2.14           -> Sanity tests for ansible.scm using ansible-core 2.14 and python 3.11

sanity-py3.11-devel          -> Sanity tests for ansible.scm using ansible-core devel and python 3.11

sanity-py3.11-milestone      -> Sanity tests for ansible.scm using ansible-core milestone and python 3.11

...

unit-py3.11-2.14             -> Unit tests for ansible.scm using ansible-core 2.14 and python 3.11

unit-py3.11-devel            -> Unit tests for ansible.scm using ansible-core devel and python 3.11

unit-py3.11-milestone        -> Unit tests for ansible.scm using ansible-core milestone and python 3.11

```



These represent the available testing environments. Each denotes the type of tests that will be run, the Python interpreter used to run the tests, and the Ansible version used to run the tests.



To run tests with a single environment, simply run the following command:



```bash

tox -e sanity-py3.11-2.14 --ansible --conf tox-ansible.ini

```



To run tests with multiple environments, simply add the environment names to the command:



```bash

tox -e sanity-py3.11-2.14,unit-py3.11-2.14 --ansible --conf tox-ansible.ini

```



To run all tests of a specific type in all available environments, use the factor `-f` flag:



```bash

tox -f unit --ansible -p auto --conf tox-ansible.ini

```



To run all tests across all available environments:



```bash

tox --ansible -p auto --conf tox-ansible.ini

```



Note: The `-p auto` flag will run multiple tests in parallel.

Note: The specific Python interpreter will need to be pre-installed on your system, e.g.:



```bash

sudo dnf install python3.10

```



To review the specific commands and configuration for each of the integration, sanity, and unit factors:



```bash

tox config --ansible --conf tox-ansible.ini

```



Generate specific GitHub action matrix as per scope mentioned with `--matrix-scope`:



```bash

tox --ansible --gh-matrix --matrix-scope unit --conf tox-ansible.ini

```



A list of dynamically generated Ansible environments will be displayed specifically for unit tests:



```

[

  {

    "description": "Unit tests using ansible 2.9 and python 3.8",

    "factors": [

      "unit",

      "py3.8",

      "2.9"

    ],

    "name": "unit-py3.8-2.9",

    "python": "3.8"

  },

  ...

  {

    "description": "Unit tests using ansible-core milestone and python 3.12",

    "factors": [

      "unit",

      "py3.12",

      "milestone"

    ],

    "name": "unit-py3.12-milestone",

    "python": "3.12"

  }

]

```



## Configuration



`tox-ansible` should be configured using a `tox-ansible.ini` file. Using a `tox-ansible.ini` file allows for the introduction of the `tox-ansible` plugin to a repository that may already have an existing `tox` configuration without conflicts. If no configuration overrides are needed, the `tox-ansible.ini` file may be empty but should be present. In addition to all `tox` supported keywords the `ansible` section and `skip` keyword are available:



```ini

# tox-ansible.ini

[ansible]

skip =

    2.9

    devel

```



This will skip tests in any environment that uses Ansible 2.9 or the devel branch. The list of strings is used for a simple string in string comparison of environment names. Here is the [guide] to override `tox-ansible` environment configuration.



[guide]: https://ansible.readthedocs.io/projects/tox-ansible/configuration/#overriding-the-configuration



## Release process



`tox-ansible` is released with [CalVer] scheme version numbers. The particular scheme we are using is `YY.MM.MICRO`, meaning that a release in March 2025 will be named `25.3.0`, and if a patch (ie, non-feature) release is required for that release, it will be named 25.3.1, even if it is released in April. The month will not increment until a new version with features or other significant changes is released. More details about calver release process can be seen [here].



[here]: https://ansible.readthedocs.io/projects/team-devtools/guides/calver/

[CalVer]: https://calver.org/



## Note to version 1.x users



Users of tox-ansible v1 should use the stable/1.x branch because the default branch is a rewrite of the plugin for tox 4.0+ which is not backward compatible with the old plugin.



Version 1 of the plugin had native support for molecule. Please see the "Running molecule scenarios" above for an alternative approach.



## License



MIT