ansible/molecule
Molecule
Molecule es un orquestador de pruebas de infraestructura y framework de pruebas diseñado para roles y colecciones de Ansible. Funciona como un gestor de entornos efímeros que levanta y destruye hosts de prueba temporales para validar código de infraestructura de forma aislada.
El proyecto se distingue por un validador de idempotencia especializado que ejecuta secuencias de automatización varias veces para asegurar que no ocurran cambios no deseados después de alcanzar el estado deseado inicial. Utiliza un modelo de aprovisionamiento basado en drivers para admitir la creación de objetivos de prueba a través de contenedores, máquinas virtuales e instancias en la nube.
La herramienta gestiona el ciclo de vida completo de las pruebas a través de orquestación basada en fases, cubriendo desde el aprovisionamiento del entorno y la convergencia hasta la validación de resultados funcionales y la destrucción de recursos. Admite la ejecución de escenarios en paralelo, la construcción de imágenes de prueba personalizadas y la integración de fuentes de inventario tanto estáticas como dinámicas para asegurar que la automatización se comporte de manera consistente en diferentes plataformas.
Features
- Idempotency Testing - Implements a specialized validator that executes automation multiple times to verify that no unintended changes occur after the initial run.
- Ansible Testing Frameworks - Provides a comprehensive framework for linting, validating, and testing Ansible roles and collections.
- State Validation - Runs full sequences of provisioning and verification to confirm playbooks achieve the intended system state.
- Driver-Based Provisioning - Implements modular drivers to provision and tear down ephemeral test targets like containers and virtual machines.
- Automated Testing Containers - Spins up ephemeral container instances as test hosts and destroys them after executing configuration playbooks.
- Infrastructure Idempotency Validators - Executes automation multiple times to ensure no unintended changes occur after the initial successful run.
- Infrastructure Idempotency Testing - Confirms that repeated applications of infrastructure code result in the same state without unexpected changes.
- Test Lifecycle Phases - Orchestrates the full test process through a sequence of distinct phases including convergence and destruction.
- Testing Lifecycle Management - Coordinates the complete testing process by mapping actions to provisioning and resource destruction phases.
- Outcome Verification - Executes verification tasks after automation to compare the actual system state against expected functional outcomes.
- Automated Infrastructure Testing - Validates Ansible roles and collections by executing them across containers, virtual machines, and cloud infrastructure.
- Ephemeral Testing Environments - Spins up and tears down isolated, short-lived container or VM instances to validate infrastructure code.
- Test Orchestration - Coordinates the lifecycle, dependencies, and execution order of infrastructure test environments.
- Test Image Templates - Builds custom container images using direct files or templates to define specific test environments.
- Dynamic Inventory Resolution - Resolves test hosts using static files or dynamic scripts to ensure production-parity environments.
- Ansible Playbooks - Provides native execution of Ansible playbooks to verify infrastructure state on provisioned test targets.
- Automation Inventory Management - Enables the use of external files and scripts to manage target machine groups for automation testing.
- Environment Verifications - Verifies that inventory configurations and dynamic sources are reachable and properly configured before test execution.
- Cross-Environment Test Harnesses - Executes test scenarios across diverse targets like Linux containers or network simulations to ensure consistent automation behavior.
- Test Sequence Control - Allows defining the custom order of testing phases to create tailored validation workflows.
- Parallel Test Execution - Runs multiple test environments and scenarios concurrently to reduce total validation time.
- Parallel Test Execution - Executes multiple test scenarios simultaneously to reduce the total duration of the infrastructure validation suite.
- Targeted Test Execution - Allows running a specific subset of test cases or full lifecycles for a named environment to isolate failures.
- Cross-Platform Test Execution - Verifies that automation code behaves consistently across different operating systems and cloud providers.
