molecule-init

Test-driven development for Ansible roles uses Molecule to create Docker-based testing environments. This Skill initializes the complete Molecule scaffolding—directories, playbooks, and configuration files—enabling you to write and validate tests before role logic, automating the entire TDD workflow from test definition through convergence and verification.

Molecule automates role testing by spinning up Docker containers, running Ansible playbooks against them, and validating outcomes. It handles prerequisite checks for Docker and Ansible, generates required config files (molecule.yml, create.yml, converge.yml, verify.yml, destroy.yml), manages dynamic inventory, and guides you through a complete test cycle.

Molecule supports Docker-based testing scenarios for Ansible roles, providing lightweight, fast container environments. This approach offers an alternative to traditional testing methods by enabling rapid iteration, parallel test execution, and consistent environments across development and CI/CD pipelines.

Yes. This Skill validates prerequisites—Docker, Ansible, and Molecule must be present in your environment. If any are missing, the setup fails and directs you to install them before proceeding with Molecule scaffolding and role testing initialization.

After creating an Ansible role, request Molecule initialization to generate the testing harness. The Skill creates the molecule/ directory structure, scenario files, and playbooks needed to run molecule test, validating your role against test cases you define in the generated verify.yml playbook.

Molecule scaffolding creates molecule.yml (main config), create.yml (instance provisioning), converge.yml (role execution), verify.yml (test validation), destroy.yml (cleanup), and requirements.yml (dependencies). These files form the complete testing harness needed for Docker-based role validation and TDD workflows.