status-go/e2e
b00ris 97c473ad7a Add group messaging MailServer test case (#515)
This e2e test exchanges a message between a group of three nodes and checks if MailServer properly responds to a request for historic messages.
2017-12-26 13:21:07 +01:00
..
accounts Issue/fix public testnet tests #424 (#438) 2017-11-07 12:46:11 -05:00
api Refactor jail part 2 (#401) 2017-11-07 12:36:42 -05:00
jail CreateAndInitCell should allow reinitializing a cell #497 (#500) 2017-12-08 22:32:30 +07:00
node Makes random panics on node manager tests less frequent (#433) 2017-11-07 12:43:49 -05:00
rpc fix failing tests in PRs from other repos, fixes #459 (#461) 2017-11-20 10:21:30 -08:00
transactions Issue/fix public testnet tests #424 (#438) 2017-11-07 12:46:11 -05:00
whisper Add group messaging MailServer test case (#515) 2017-12-26 13:21:07 +01:00
README.md Update regards review 2017-10-25 23:07:50 +01:00
suites.go fix failing tests in PRs from other repos, fixes #459 (#461) 2017-11-20 10:21:30 -08:00
testing.go Update readme and update code for testing 2017-10-24 11:23:53 +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

To use the ropsten network for testing using network name:

go test -v ./e2e/... -network=ropsten

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

go test -v ./e2e/... -network=4

Run

make test-e2e