Molecule

Molecule is designed to aid in the development and testing of Ansible roles. Molecule provides support for testing with multiple instances, operating systems and distributions, virtualization providers, test frameworks and testing scenarios. Molecule is opinionated in order to encourage an approach that results in consistently developed roles that are well-written, easily understood and maintained.

Molecule uses Ansible playbooks to exercise the role and its associated tests. Molecule supports any provider [1] that Ansible supports.

[1]	Providers can be bare-metal, virtual, cloud or containers. If Ansible can use it, Molecule can test it. Molecule simply leverages Ansible’s module system to manage instances.

Documentation

• Current Release
• Upcoming Release

Ansible Support

• 2.2.2.0
• 2.3.0.0

License

MIT

The logo is licensed under the Creative Commons NoDerivatives 4.0 License. If you have some other use in mind, contact us.

Contents:

• Usage
  • Quick Start
  • Check
  • Converge
  • Create
  • Dependency
  • Destroy
  • Idempotence
  • Init
  • Lint
  • List
  • Login
  • Syntax
  • Test
  • Verify
• Configuration
  • Config
  • Variable Substitution
  • Dependency
    • Ansible Galaxy
    • Gilt
  • Driver
    • Docker
    • EC2
    • LXC
    • LXD
    • Openstack
    • Static
    • Vagrant
    • Molecule Vagrant Module
  • Lint
    • Ansible Lint
  • Platforms
  • Provisioner
    • Ansible
  • Scenario
  • State
  • Verifier
    • Goss
    • Testinfra
• Porting Guide
• Testing
  • Dependencies
  • Full
  • Unit
  • Functional
  • Formatting
  • Linting
  • LXC
  • LXD
  • Continuous integration
    • Travis CI
    • Tox
• Contributing
  • IRC
  • Installing from source
  • Testing
  • Ansible Modules
• Development
  • Branches
  • Release Engineering
    • Pre-release
    • Release
    • Post-release
  • Roadmap
• History
  • 2.0
    • Important Changes
    • Breaking Changes
  • 1.25
  • 1.24
  • 1.23.3
  • 1.23.2
  • 1.23.1
  • 1.23
  • 1.22
  • 1.21.1
  • 1.21
    • Breaking Changes
  • 1.20.3
  • 1.20.2
  • 1.20.1
  • 1.20
    • Breaking Changes
  • 1.19.3
  • 1.19.2
  • 1.19.1
  • 1.19
  • 1.18.1
  • 1.18
  • 1.17.3
  • 1.17.2
  • 1.17.1
  • 1.17
  • 1.16.1
    • Breaking Changes
  • 1.16
  • 1.15
    • Breaking Changes
  • 1.14.1
  • 1.14
    • Breaking Changes
  • 1.13
  • 1.12.6
  • 1.12.5
  • 1.12.4
  • 1.12.3
  • 1.12.2
  • 1.12.1
  • 1.12
    • Breaking Changes
  • 1.11.5
  • 1.11.4
  • 1.11.3
  • 1.11.2
  • 1.11.1
  • 1.11
    • Breaking Changes
  • 1.10.3
    • Note
  • 1.10.2
  • 1.10.1
  • 1.10
    • Breaking Changes
  • 1.9.1
  • 1.9
    • Breaking Changes
  • 1.8.4
  • 1.8.3
  • 1.8.2
  • 1.8.1
  • 1.8
  • 1.7
  • 1.6.3
  • 1.6.2
  • 1.6.1
  • 1.6
  • 1.5.1
  • 1.5
  • 1.4.2
  • 1.4.1
  • 1.4
  • 1.3
  • 1.2.4
  • 1.2.3
  • 1.2.2
  • 1.2.1
  • 1.2
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1
  • 1.0.6
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0
• Credits
  • Development Leads
  • Core Committers
  • Contributors
• FAQ
  • Why does Molecule make so many shell calls?
  • Why does Molecule only support ansible 2.2 and 2.3?
  • Why are playbooks used to provision instances?
  • Have you thought about using Ansible’s python API instead of playbooks?
  • Why are there multiple scenario directories and molecule.yml files?
  • Are there similar tools to Molecule?

Indices and tables

• Index
• Module Index
• Search Page