History

Przemyslaw Rzad 54858ae597 Molecule tests for deploying repository (#194 ) * Squashed commits * All jobs * Rollback changes * Dependencies * Remove .git checking * Resolve path issues * New way of copying repository. * Test non existing .git * New repo task * Typo * Do not fail mkdir if folder exists * Test double task * zipping the archives * Increase no_output_timeout because of slowly installing apt-get		2019-09-06 15:24:30 +02:00
..
molecule	Molecule tests for deploying repository (#194 )	2019-09-06 15:24:30 +02:00
docker-compose.yml	Move molecule to deployment-e2e (#196 )	2019-08-29 10:30:34 +02:00
Dockerfile	Move molecule to deployment-e2e (#196 )	2019-08-29 10:30:34 +02:00
molecule.sh	Move molecule to deployment-e2e (#196 )	2019-08-29 10:30:34 +02:00
README.md	Move molecule to deployment-e2e (#196 )	2019-08-29 10:30:34 +02:00

README.md

POA TokenBridge / Deployment Testing

The deployment playbooks are tested using Molecule.

Push remote branch

The deployment playbooks are cloning the monorepository on target hosts, using your current local git branch name. If the branch does not exists on remote, you need to push it.

git push

Alternatively, if there are no changes except the playbooks, you can use the master branch:

CIRCLE_BRANCH=master ./molecule.sh <scenario_name>

In this case master branch will be used as a codebase for Monitor, UI, Oracle and Contracts deployed by your local playbook.

Run the tests

CIRCLE_BRANCH=master ./molecule.sh <scenario_name>

Available scenarios:

Scenario	Description
oracle	Deploys and checks standalone Oracle on Ubuntu host
ui	Deploys and checks standalone UI on Ubuntu host

Ultimate E2E tests

For information on the Ultimate tests, please refer to Ultimate.