status-go/t/e2e
Andrea Maria Piana 7387049d4b Upgrade linter and address issues 2020-12-28 16:55:14 +01:00
..
accounts Fix tests and lint 2020-12-17 14:10:00 +01:00
api Upgrade linter and address issues 2020-12-28 16:55:14 +01:00
node Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
rpc Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
services Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
transactions Fix tests and lint 2020-12-17 14:10:00 +01:00
README.md Streamline configuration in status-go. Part of #1180 (#1183) 2018-09-13 18:31:29 +02:00
suites.go [status-im/status-react#9942] Upgradable paths in configs 2020-02-03 20:02:01 +02:00
testing.go Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00

README.md

e2e

This package contains all e2e tests divided into subpackages which represents (or should represent) business domains like transactions, chat etc.

These tests are run against public testnets: Ropsten and Rinkeby.

e2e package contains a few utilities which are described in a godoc.

Flags

1. -network

The -network flag is used to provide either a network id or network name which specifies the ethereum network to use for running all test. It by default uses the StatusChain network.

Usage

First of all you need to export an ACCOUNT_PASSWORD environment variable. It should be a passphrase that was used to generate accounts used in tests. If you don't know this variable for default accounts you will have to create your own accounts and request some funds from rinkeby or ropsten faucet. Please see Preparation section for details.

To use the ropsten network for testing using network name:

ACCOUNT_PASSWORD=test go test -v ./t/e2e/... -p=1 -network=ropsten

To use the rinkeby network with chain id 4 for testing:

ACCOUNT_PASSWORD=test go test -v ./t/e2e/... -p=1 -network=4

Preparation

You will need geth in your PATH. Please visit: https://www.ethereum.org/cli. Once installed - generate 2 accounts and remember the passphrase for them, so run this command twice:

geth account new --keystore=static/keys/
Your new account is locked with a password. Please give a password. Do not forget this password.
Passphrase:
Repeat passphrase:
Address: {b6120ddd881593537c2bd4280bae509ec94b1a6b}

We expect that accounts will be named in a certain way:

pushd static/keys/
mv UTC--2018-01-26T13-46-53.657752811Z--b6120ddd881593537c2bd4280bae509ec94b1a6b test-account1.pk
mv UTC--2018-01-26T13-47-49.289567120Z--9f04dc05c4c3ec3b8b1f36f7d7d153f3934b1f07 test-account2.pk
popd

Update config for tests with new accounts t/config/public-chain-accounts.json:

{
  "Account1": {
    "Address": "0xb6120ddd881593537c2bd4280bae509ec94b1a6b"
  },
  "Account2": {
    "Address": "0x9f04dc05c4c3ec3b8b1f36f7d7d153f3934b1f07"
  }
}

Embed keys as a binary data, you will need to install npm tool and web3.js lib:

make generate

As a final step request funds from faucet for a chosen network:

Finally, you are ready to run tests!