History

Frank Mueller 1c8d32c451 Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 ) During CI tests non-deterministic failures with "no suitable peers available" happened. Reason is a not finished synchronisation after starting of node. Added and integrated an EnsureSychronization() almost solved it, but overlapped with new added EnsureNodeSync() in merged develop. Failure stayed, so exchange new algorithm in EsureNodeSync() with former one.		2017-10-21 20:04:07 +03:00
..
accounts	Extract e2e tests to a separate package (#375 )	2017-10-11 17:20:51 +03:00
api	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 )	2017-10-21 20:04:07 +03:00
jail	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 )	2017-10-21 20:04:07 +03:00
node	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 )	2017-10-21 20:04:07 +03:00
rpc	Fix make lint warnings (#417 )	2017-10-20 12:06:22 +03:00
transactions	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 )	2017-10-21 20:04:07 +03:00
whisper	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 )	2017-10-21 20:04:07 +03:00
README.md	Extract e2e tests to a separate package (#375 )	2017-10-11 17:20:51 +03:00
suites.go	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410 )	2017-10-21 20:04:07 +03:00
testing.go	Fix make lint warnings (#417 )	2017-10-20 12:06:22 +03:00

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.

Run

make test-e2e