skip to content W3C SVG

Testing

The testing process consists in deploying the complete playbook (full.yml) to a fresh virtual machine using molecule and vagrant.

Steps that will be made:

  1. Destroy pre-existing instances.
  2. Not used. Fetch dependencies (git or ansible-galaxy).
  3. Syntax check.
  4. Create instances.
  5. Prepare instances (install python).
  6. Converge: deploy the playbook.
  7. Idempotence: re-run the playbook.
  8. Lint: ansible good practices.
  9. Not used. Side effects.
  10. Verify: run tests.
  11. Destroy instances.
└── default
    ├── destroy
    ├── dependency
    ├── syntax
    ├── create
    ├── prepare
    ├── converge
    ├── idempotence
    ├── lint
    ├── side_effect
    ├── verify
    └── destroy

Note: you can run a step individually with: molecule [step].

Setup molecule with vagrant

You will need:

  • virtualbox
  • vagrant
  • Python tools, a virtualenv (python2) is recommended.

After installing virtualbox and vagrant, you have to download molecule on a new virtualenv:

$ cd
$ virtualenv --no-site-packages .venv
$ source .env/bin/activate
$ cd WHITECLUBTREPOPATH/
$ mkdir library
$ cd library
$ wget https://raw.githubusercontent.com/Nordeus/ansible_iptables_raw/master/iptables_raw.py
$ cd ..
$ pip install molecule testinfra python-vagrant ansible yamllint ansible-lint
$ molecule test

Also, optionally, you can use a docker registry mirror in your local machine (optional). You can install it following this guide: docker-doc. TL;DR: docker run -d -p 5000:5000 --restart always --name registry -e "REGISTRY_DELETE_ENABLED=true" -e "REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io" registry:2

If you don't want to use it, comment or delete `docker_registry_mirror: http://172.16.100.1:5000`
in *molecule/default/molecule.yml*.

If you use `iptables` on your host machine:
`iptables -A INPUT -s 172.16.100.0/24 -i vboxnet0 -p tcp -m tcp --dport 5000 -j ACCEPT`.

Configuration

The main configuration file is molecule/default/molecule.yml.

Process

To run every step mentioned above: molecule test.

That’s all.

Workflow

  1. Change stuff and write its tests.
  2. molecule test
  3. Correct the errors.
  4. Re run only the failing part. E.g. molecule idempotence.

Tips

  • You can connect to the virtual machine with: molecule login. This is really useful for debugging.
  • You can run only the tests with molecule verify.

  • It is useful to add this lines to your local /etc/hosts file, so that you can access the testing virtual machine via web:

    ## anarres
172.16.100.12	anarres.local
172.16.100.12	git.anarres.local
172.16.100.12	cloud.anarres.local
172.16.100.12	drone-github.anarres.local

  • You can get more information from molecule running it in debug mode: molecule --debug test.