25
1
mirror of https://github.com/processone/ejabberd.git synced 2024-11-20 16:15:59 +01:00
xmpp.chapril.org-ejabberd/test/docker
2019-07-18 17:56:11 +02:00
..
db Initial Docker environment to run ejabberd test suite 2019-05-07 17:59:05 +02:00
docker-compose.yml Initial Docker environment to run ejabberd test suite 2019-05-07 17:59:05 +02:00
README.md Mention about a few Riak tests being broken 2019-07-18 17:56:11 +02:00

Docker database images to run ejabberd tests

Starting databases

You can start the Docker environment with Docker Compose, from ejabberd repository root.

The following command will launch MySQL, PostgreSQL, Redis and Riak, and keep the console attached to it.

mkdir test/docker/db/mysql/data
mkdir test/docker/db/postgres/data
mkdir test/docker/db/riak/data
(cd test/docker; docker-compose up)

You can stop all the databases with CTRL-C.

Running tests

Before running the test, you can ensure there is no running instance of Erlang common test tool. You can run the following command, especially if all test are skipped with an eaddrinuse error:

pkill -9 ct_run

You can run tests with (from ejabberd repository root):

make test

At the moment, starting from Erlang 21, some Riak tests are broken because Riak client is not compliant with OTP 21+.

To run everything except Riak tests, you can use the following command:

CT_BACKENDS=mnesia,redis,mysql,pgsql,sqlite,ldap,extauth rebar ct suites=ejabberd

Cleaning up the test environment

You can fully clean up the environment with:

(cd test/docker; docker-compose down)

If you want to clean the data, you can remove the data directories after the docker-compose down command:

rm -rf test/docker/db/mysql/data
rm -rf test/docker/db/postgres/data
rm -rf test/docker/db/riak/data