Testing¶

Testing can be done using the provided Vagrantfile or by installing Docker and use Molecule locally.

For execute the molecule test you can use the Docker Image described at Molecule page.

docker run --rm -it \
    -v $(pwd):/tmp/$(basename "${PWD}"):ro \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -e mc_accept_eula=${mc_accept_eula} \
    -w /tmp/$(basename "${PWD}") \
    retr0h/molecule:latest \
    sudo molecule test --all

after execute drink a pot of tee, coffee or some beer, all molecule scenarios will be run more than 40 minute

Testing with Molecule¶

The Tests are impemented with Molecule

molecule test -s spigot

Molecule Tips¶

For the development and debugging it is easyer and faster to execute the Molecule sequenzes step by step.
First you must start the container with molecule create, after the containers started, you can execute the Role/Playbook molecule converge.
Now, when all the steps are finished, you can execute the Integration Tests with molecule verify

Note

For Debugging the role take a look into the container with docker exec -t -i centos7 /bin/bash

Testing with Vagrant¶

This role includes a Vagrantfile used for Exploratory testing.

If you want to use this vagrant machine follow this steps:

Install Vagrant and VirtualBox.
1. Accept the Minecraft EULA with setting a Environment Property like: export mc_accept_eula=true
Run vagrant up from the same directory as the Vagrantfile in this repository.

Note

Now, you can start the game and conntecting again our server e.g. localhost:25565 and test the changes.

3. for manual lookups you can connect over SSH into the VM with: vagrant ssh

Note

If the Vagrant box allways exists, you can reexecute the Playbook with vagrant rsync && vagrant provision