mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-23 11:57:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
1b62e92159
prysm-pulse/endtoend
History
Raul Jordan ed529965af Fix Up SSZ Cache Branch Recomputation (#4558) 
* e2e ssz cache busting
* use ssz cache for e2e
* caching ensure
* fix up the cache even more
* gazelle
* formatting
* formatting
* add back cache for val registry
* sync
* fix up commented item
* add attestations
* Merge branch 'master' into e2e-ssz-cache
* Merge branch 'master' into e2e-ssz-cache
* Merge branch 'e2e-ssz-cache' of github.com:prysmaticlabs/prysm into e2e-ssz-cache
* formatting
* gaz
* Merge branch 'master' into e2e-ssz-cache
* resolve comments
* Merge branch 'master' into e2e-ssz-cache
* naming of test
* Merge refs/heads/master into e2e-ssz-cache
* Merge refs/heads/master into e2e-ssz-cache
2020-01-16 21:40:09 +00:00
..
evaluators Efficient computation of epoch participation (#4430) 2020-01-07 19:28:25 +00:00
beacon_node.go Fix Up SSZ Cache Branch Recomputation (#4558) 2020-01-16 21:40:09 +00:00
BUILD.bazel Build docker images for non-root user (#4320) 2019-12-18 20:52:25 +00:00
demo_e2e_test.go Update run time to v0.9.3 (#4154) 2020-01-07 18:47:39 +00:00
endtoend_test.go Efficient computation of epoch participation (#4430) 2020-01-07 19:28:25 +00:00
epochTimer.go End To End Tests for Demo and Minimal config (#3932) 2019-11-15 13:56:26 -05:00
eth1.go Vastly improve E2E logs and add README (#4440) 2020-01-07 17:00:51 +00:00
minimal_e2e_test.go Fix Up SSZ Cache Branch Recomputation (#4558) 2020-01-16 21:40:09 +00:00
README.md Vastly improve E2E logs and add README (#4440) 2020-01-07 17:00:51 +00:00
validator.go Add double proposal protection to validator client (#4460) 2020-01-15 17:23:39 -05: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.

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 5 epochs
  • Demo Config - 4 beacon nodes, 64 validators, running for 5 epochs

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