Commit Graph

13 Commits

Author SHA1 Message Date
Evgeny Danilenko 209d5fed74 Issue/fix public testnet tests #424 (#438)
* Accounts are now encrypted with a strong passphrase.
* The encrypted passphrase is stored in .travis.yml
* Public testnet tests are now run after tests on a private net
2017-11-07 12:46:11 -05:00
Ivan Tomilov 21beb685b4 Add -network flag for Makefile to chose a network to run tests on #430
PR adds test flag -network to e2e pacakge, for the selection of the desired blockchain network for running tests. It updates readme to demonstrates usage of flag.
2017-10-26 22:51:04 +03:00
Ivan Tomilov 004aa83d84 Remove unnecessary return 2017-10-26 22:36:45 +03:00
Alexander Ewetumo efa10134e8 Fixing missing imports 2017-10-26 14:14:11 +01:00
Alexander Ewetumo 1cc90541da Update makefiles and make changes regards review 2017-10-26 14:11:24 +01:00
Alexander Ewetumo 681a2d2d83 Skip test requiring network url for statuschain 2017-10-26 13:33:42 +01:00
Alexander Ewetumo 4d356e0873 Update regards review 2017-10-25 23:07:50 +01:00
Alexander Ewetumo 468a52737a Fixing changes and url bug in accounts and transactions 2017-10-25 13:37:42 +01:00
Ivan Tomilov 39cc60b8a7 Fixed make lint 2017-10-24 19:48:31 +03:00
Alexander Ewetumo a257d1c201 Fix errors on network chain id validation in tests 2017-10-23 18:18:09 +01:00
Alexander Ewetumo 7718bd5990 Move all tests to retrieve NetworkId from flag or default to statuschain 2017-10-23 17:03:07 +01:00
Ivan Tomilov c500fbc423 Made all tests run on StatusChain instead of Rinkeby or Ropsten (#426)
The reason is that we don't currently have a possibility to run tests on public testnets without compromising accounts and funds on them.
2017-10-23 14:05:52 +03:00
Adam Babik 281b304edb Extract e2e tests to a separate package (#375)
This change moves our e2e tests into a separate package to make room for proper unit and integration tests.

This is Phase 1 described in #371.

Changes:

Makefile has separate directives to run unit/integration tests and e2e tests,
CI runs unit/integration tests first and then e2e tests,
E2e tests are in reliability order, i.e. the least reliable tests are run in the end to be sure that nothing else is broken,
Some tests are fixed or quarantined.
2017-10-11 17:20:51 +03:00