tokenbridge/deployment-e2e
Gerardo Nardelli 7a54e584d5 Support alternative receiver in Oracle (#221)
* Add transfer watcher
* Filter userRequestForAffirmation events in Transfer events
* Add extended oracle composer file
2019-10-29 17:55:47 +03:00
..
molecule Support alternative receiver in Oracle (#221) 2019-10-29 17:55:47 +03:00
docker-compose.yml Move molecule to deployment-e2e (#196) 2019-08-29 10:30:34 +02:00
Dockerfile Remove rsync dependency (#213) 2019-09-16 18:34:42 +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

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.