README.md

See the README in deployer/contracts for more info on deployment of the contracts.

Importantly, ensure you've run the below before starting the tests:

cd path/to/deployer
truffle compile --all

To run a specific test:

Note: in the steps below, you can replace -f docker-compose.remote.pull.yml with one of the other provided docker-compose files, such as -f docker-compose.remote.push.yml.

Note, however, that the default docker-compose.yml file is a bit more fiddly, because it relies on contracts being deployed via truffle with your application. Tests aren't provided for that file yet.

First, compile the contracts:

cd deployer
truffle compile
cd ..

MerkleTreeController.test.js

This test relies on the deployer microservice's url 'http://deployer:80' being discoverable by itself. We achieve this easily by running the 'main' docker-compose script first:

In one terminal window:
docker-compose up

Then in another terminal window:
docker-compose -f docker-compose.remote.pull.yml run --rm deployer npx mocha --exit --require @babel/register 'test/MerkleTreeController.test.js'

deployment.test.js

docker-compose -f docker-compose.remote.pull.yml run --rm deployer npx mocha --exit --require @babel/register 'test/deployment.test.js'

Understanding this command:
docker-compose -f docker-compose.remote.pull.yml selects the docker-compose file to use.
run --rm deployer creates an instance of the deployer microservice (along with any dependent service containers) and runs whatever command follows.
npx mocha run mocha.
--exit exits the mocha test once its finished (although this will leave the containers still running).
--require @babel/register to help mocha understand the js syntax used.

After testing

docker-compose down -v to kill the docker containers, volumes, and networks.