laconicd/tests-solidity
Federico Kunze 4a619b1e1b
faucet: remove module (#678)
* changelog v0.4.0

* faucet: remove module

* changelog

* codecov
2021-01-08 10:25:02 -03:00
..
suites update tools configs (#611) 2020-11-24 16:43:08 +01:00
.gitattributes tests: add solidity test suites (#487) 2020-09-01 17:16:28 -04:00
.gitignore tests: add solidity test suites (#487) 2020-09-01 17:16:28 -04:00
init-test-node.sh faucet: remove module (#678) 2021-01-08 10:25:02 -03:00
package.json tests: add solidity test suites (#487) 2020-09-01 17:16:28 -04:00
README.md update chain-id format (#542) 2020-09-24 14:50:47 -03:00
yarn.lock build(deps): bump ini from 1.3.5 to 1.3.8 in /tests-solidity (#657) 2020-12-14 15:36:02 +01:00

Solidity tests

Increasingly difficult tests are provided:

Quick start

Prerequisite: in the repo's root, run make install to install the ethermintd and ethermintcli binaries. When done, come back to this directory.

Prerequisite: install the individual solidity packages. They're set up as individual reops in a yarn monorepo workspace. Install them all via yarn install.

To run the tests, start three terminals (or two, if you run ethermintd with &).

In the first, run ethermintd:

./init-test-node.sh

In the second, run ethermintcli as mentioned in the script's output:

ethermintcli rest-server --laddr "tcp://localhost:8545" --unlock-key localkey,user1,user2 --chain-id "ethermint-1337" --trace --wsport 8546

You will now have three ethereum accounts unlocked in the test node:

  • 0x3b7252d007059ffc82d16d022da3cbf9992d2f70 (Validator)
  • 0xddd64b4712f7c8f1ace3c145c950339eddaf221d (User 1)
  • 0x0f54f47bf9b8e317b214ccd6a7c3e38b893cd7f0 (user 2)

From here, in your other available terminal, go into any of the tests and run yarn test-ethermint. You should see ethermintd accepting transactions and producing blocks. You should be able to query for any transaction via:

  • ethermintcli query tx <cosmos-sdk tx>
  • curl localhost:8545 -H "Content-Type:application/json" -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["<ethereum tx>"],"id":1}'

And obviously more, via the Ethereum JSON-RPC API).

When in doubt, you can also run the tests against a Ganache instance via yarn test-ganache, to make sure they are behaving correctly.

Test node

The init-test-node.sh script sets up ethermint with the following accounts:

  • eth18de995q8qk0leqk3d5pzmg7tlxvj6tmsku084d (Validator)
    • 0x3b7252d007059ffc82d16d022da3cbf9992d2f70
  • eth1mhtyk3cj7ly0rt8rc9zuj5pnnmw67gsapygwyq (User 1)
    • 0xddd64b4712f7c8f1ace3c145c950339eddaf221d
  • eth1pa20g7lehr330vs5ent20slr3wyne4lsy8qae3 (user 2)
    • 0x0f54f47bf9b8e317b214ccd6a7c3e38b893cd7f0

Each with roughly 100 ETH available (1e18 photon).

Running ethermintcli list keys should output:

[
  {
    "name": "localkey",
    "type": "local",
    "address": "eth18de995q8qk0leqk3d5pzmg7tlxvj6tmsku084d",
    "pubkey": "ethpub1pfqnmk6pq3ycjs34vv4n6rkty89f6m02qcsal3ecdzn7a3uunx0e5ly0846pzg903hxf2zp5gq4grh8jcatcemfrscdfl797zhg5crkcsx43gujzppge3n"
  },
  {
    "name": "user1",
    "type": "local",
    "address": "eth1mhtyk3cj7ly0rt8rc9zuj5pnnmw67gsapygwyq",
    "pubkey": "ethpub1pfqnmk6pq3wrkx6lh7uug8ss0thggact3n49m5gkmpca4vylldpur5qrept57e0rrxfmeq5mp5xt3cyf4kys53qcv66qxttv970das69hlpkf8cnyd2a2x"
  },
  {
    "name": "user2",
    "type": "local",
    "address": "eth1pa20g7lehr330vs5ent20slr3wyne4lsy8qae3",
    "pubkey": "ethpub1pfqnmk6pq3art9y45zw5ntyktt2qrt0skmsl0ux9qwk8458ed3d8sgnrs99zlgvj3rt2vggvkh0x56hffugwsyddwqla48npx46pglgs6xhcqpall58tgn"
  }
]

And running:

curl localhost:8545 -H "Content-Type:application/json" -X POST --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[],"id":1}'

Should output:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": [
    "0x3b7252d007059ffc82d16d022da3cbf9992d2f70",
    "0xddd64b4712f7c8f1ace3c145c950339eddaf221d",
    "0x0f54f47bf9b8e317b214ccd6a7c3e38b893cd7f0"
  ]
}