Ansible Automation Ansible Testing with Molecule 2

Question 1

In Molecule's molecule.yml, what does the 'platforms' section define?

Accepted Answer

The test instances (containers/VMs) to create, including their names, images, and configuration

Answer

The 'platforms' section specifies what test instances Molecule should create—their names, Docker images, OS versions, etc.

Question 2

What is Molecule's 'idempotency' test and why is it important?

Accepted Answer

Molecule runs the converge playbook twice and fails if any task reports 'changed' on the second run, verifying that the role doesn't make unnecessary changes

Answer

The idempotency check enforces a core Ansible principle—a properly written role should only make changes when needed, not on every run.

Question 3

How do you run Molecule tests for a specific scenario when multiple scenarios exist?

Accepted Answer

molecule test --scenario-name scenarioname

Answer

The '--scenario-name' flag (or '-s' shorthand) specifies which scenario to run when a role has multiple test scenarios.

Question 4

What is the purpose of Molecule's 'prepare' phase?

Accepted Answer

It runs a prepare.yml playbook to configure test prerequisites on instances before the role under test is applied

Answer

The prepare phase runs before converge to set up any prerequisites that the role expects (users, directories, packages) without those prerequisites being part of the role itself.

Question 5

How does Molecule integrate with CI/CD pipelines like GitHub Actions or GitLab CI?

Accepted Answer

Molecule runs as a standard CLI tool in pipeline jobs; Docker-in-Docker or Docker socket mounting is needed for the Docker driver

Answer

Molecule is a standard Python CLI tool that runs in any CI environment with Docker and Python available.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Ansible Testing with Molecule 2