mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-28 14:17:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
07ba594023
prysm-pulse/endtoend
History
Ivan Martinez ad01bfbcde Add sync test to E2E (#4654) 
* Complete evaluator for chain consensus

* Add sync e2e test

* Cleanup

* Rename

* Add tad more offset for correct head

* Change offset to middle of slot

* Change head block root to head epoch

* comment

* Fix eth1

* Address comments

* Gazelle

* Change to use file

* Change to use reader

* Use fil
2020-01-28 13:16:00 -06:00
..
evaluators Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
beacon_node.go Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
BUILD.bazel Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
demo_e2e_test.go Part 1 of block chain service refactor - move process block (#4670) 2020-01-27 13:48:16 -08:00
endtoend_test.go Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
epochTimer.go End To End Tests for Demo and Minimal config (#3932) 2019-11-15 13:56:26 -05:00
eth1.go Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
helpers.go Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
minimal_e2e_test.go Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
README.md Allow easy plugin of featureflags into E2E (#4659) 2020-01-26 21:42:10 -05:00
validator.go Improve E2E to be more consistent with timing, and allow for custom flags (#4620) 2020-01-25 15:39:56 +08:00

README.md

End-to-end Testing Package

This is the main project folder of the end-to-end testing suite for Prysm. This performs a full end-to-end test for Prysm, including spinning up an ETH1 dev chain, sending deposits to the deposit contract, and making sure the beacon node and it's validators are running and performing properly for a few epochs. It also performs a test on a syncing node, and supports featureflags to allow easy E2E testing of experimental features.

How it works

Through the end2EndConfig struct, you can declare several options such as how many epochs the test should run for, and what BeaconConfig the test should use. You can also declare how many beacon nodes and validator clients are run, the E2E will automatically divide the validators evently among the beacon nodes.

In order to "evaluate" the state of the beacon chain while the E2E is running, there are Evaluators that use the beacon chain node API to determine if the network is performing as it should. This can evaluate for conditions like validator activation, finalization, validator participation and more.

Evaluators have 3 parts, the name for it's test name, a policy which declares which epoch(s) the evaluator should run, and then the evaluation which uses the beacon chain API to determine if the beacon chain passes certain conditions like finality.

Current end-to-end tests

  • Minimal Config - 4 beacon nodes, 64 validators, running for 6 epochs
  • Demo Config - 2 beacon nodes, 16,384 validators, running for 5 epochs Disabled for now

Instructions

If you wish to run all the E2E tests, you can run them through bazel with:

bazel test //endtoend:go_default_test --test_output=streamed

To test only for a specific config, run:

bazel test //endtoend:go_default_test --test_output=streamed --test_filter=TestEndToEnd_DemoConfig