mig/testing
Zack Mullaly 5b386c1a29
Removing unnecessary blank lines
2018-11-22 15:39:35 -05:00
..
integration/api test should look for >= 1 row because running it multiple times shouldn't be a cause for failure 2018-11-13 15:14:37 -05:00
README.md Update docker exec command to use postgres name 2018-11-07 13:55:54 -06:00
agent.cfg Removing unnecessary blank lines 2018-11-22 15:39:35 -05:00
api.cfg Got our first integration test against postgres working 2018-10-12 13:06:40 -04:00
docker-compose.yml Working on dockerized infrastructure for testing the API against 2018-10-12 10:50:34 -04:00
init_migapi_db.sql No longer have need for the relation between agents and actions 2018-11-13 14:59:49 -05:00

README.md

Testing

This directory contains files that support testing MIG services such as the API against dockerized backend infrastructure. In particular, the docker-compose.yml file sets up Postgres and RabbitMQ instances that we can connect to from outside Docker.

Usage

First create the Docker containers

docker-compose -f ./docker-compose.yml up -d

Next, get a bash session in the Postgres container. Assuming the container name for Postgres (obtained by running docker ps) is testing_postgres_1, run the following to enter the container and then set up Postgres.

docker exec -it testing_postgres_1 bash
psql -c "CREATE DATABASE mig;"
psql -f /var/lib/db/init_migapi_db.sql mig
exit