mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 21:07:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
ecea979b60
prysm-pulse/endtoend
History
Ivan Martinez 4fb3307de3
Add Slasher double block detection to E2E (#5936) 
* WIP double block slashings e2e
* Add double block detection to E2E
* Remove unused function
* Respond to feedback
* Remove unneeded util
* Merge branch 'master' of github.com:prysmaticlabs/prysm into e2e-double-block
* Add comments for clarity on conns
2020-05-21 06:02:40 +00:00
..
components Fix test setup and change participation min back to 100% (#5791) 2020-05-09 15:11:10 -05:00
evaluators Add Slasher double block detection to E2E (#5936) 2020-05-21 06:02:40 +00:00
helpers libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
params Fix test setup and change participation min back to 100% (#5791) 2020-05-09 15:11:10 -05:00
types Add Slasher double block detection to E2E (#5936) 2020-05-21 06:02:40 +00:00
BUILD.bazel Properly Divide SecondsPerSlot Into Milliseconds (#5821) 2020-05-13 11:28:17 +08:00
endtoend_test.go Properly Divide SecondsPerSlot Into Milliseconds (#5821) 2020-05-13 11:28:17 +08:00
long_minimal_e2e_test.go Fix test setup and change participation min back to 100% (#5791) 2020-05-09 15:11:10 -05:00
minimal_antiflake_e2e_1_test.go Fix test setup and change participation min back to 100% (#5791) 2020-05-09 15:11:10 -05:00
minimal_antiflake_e2e_2_test.go Fix test setup and change participation min back to 100% (#5791) 2020-05-09 15:11:10 -05:00
minimal_e2e_test.go Fix test setup and change participation min back to 100% (#5791) 2020-05-09 15:11:10 -05:00
minimal_slashing_e2e_test.go Add Slasher double block detection to E2E (#5936) 2020-05-21 06:02:40 +00:00
README.md Other Package Godocs for Prysm (#5681) 2020-04-29 21:32:39 +00: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 its 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
  • Mainnet 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 --test_arg=-test.v --nocache_test_results

To run the anti-flake E2E tests, run:

bazel test //endtoend:go_default_test --test_output=streamed --test_filter=TestEndToEnd_AntiFlake_MinimalConfig --test_arg=-test.v --nocache_test_results