UI for Inter Protocol PSM
yarn dev
to start a local HMR server.
For bugs and feature requests, open a new issue.
For PRs, develop against the main branch.
http://psm.inter.trade serves the latest build of the beta
branch.
To deploy, push to that branch. e.g. if you've qualified main,
git push origin main:beta
E2E tests have been written in order to test the dapp as well as to perform automated testing on emerynet/devnet when upgrading the chain
There are two ways to run the tests:
To run tests on your local machine, first you need to start the frontend server:
yarn dev
If you plan to run tests with CYPRESS_AGORIC_NET=local
, you must start the a3p
chain beforehand. To do this, use the following command:
docker run -d -p 26657:26657 -p 1317:1317 -p 9090:9090 ghcr.io/agoric/agoric-3-proposals:latest
Alternatively, you can create an a3p
chain from a specific branch in your agoric-sdk
repository. To do this, navigate to the a3p-integration
directory in your agoric-sdk
repository. Install all necessary dependencies and build the project with:
yarn && yarn build
Once the build is complete, locate the Docker image you just created by running:
docker images
Find the hash of your new image and start the container using the hash:
docker run -p 26657:26657 -p 1317:1317 -p 9090:9090 {hash}
Note: the tests use chrome browser by default so they require it to be installed
Next, run the tests using the following command:
CYPRESS_AGORIC_NET=<network> yarn test:e2e
where <network>
can be: local
,emerynet
,devnet
, xnet
or ollinet
.
To run the tests on github, you can use the workflow trigger to run the tests.
Go to: Actions > E2E Tests (On the left sidebar) > Run Workflow
It provides a handful of parameters that can be used to modify the run according to your needs
- you can change the branch on which the tests run
- you can change the network on which to run the tests
- you can set a custom mnemonic of the wallet you want to use during the tests.
To display a notice banner in the app, in the network-config (e.g. https://main.agoric.net/network-config), add an entry to notices
as demonstrated:
{
...
"notices": [
{
"start": "2020-01-01",
"end": "2040-01-01",
"message": "Hello world"
}
]
}