mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-26 05:17:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
3380d14475
prysm-pulse/endtoend
History
terence tsao d8c26590ca
Prune dangling states in DB upon start up (#4697) 
* Add pruneGarbageState and test
* Comments
* Update beacon-chain/blockchain/service.go

Co-Authored-By: Ivan Martinez <ivanthegreatdev@gmail.com>
* Update beacon-chain/blockchain/service.go

Co-Authored-By: Ivan Martinez <ivanthegreatdev@gmail.com>
* Update beacon-chain/blockchain/service.go

Co-Authored-By: Ivan Martinez <ivanthegreatdev@gmail.com>
* Fixed test
* Merge refs/heads/master into prune-start-up
* Fixed test
2020-01-31 23:15:35 +00:00
..
evaluators Make E2E more resilient, check balance and participation every epoch (#4679) 2020-01-29 16:14:10 -08:00
beacon_node.go Make E2E more consistent, change log file setup (#4696) 2020-01-31 00:16:36 +00:00
BUILD.bazel Add sync test to E2E (#4654) 2020-01-28 13:16:00 -06:00
demo_e2e_test.go Replace no-genesis-delay with custom-genesis-delay (#4678) 2020-01-28 21:07:43 +00:00
endtoend_test.go Prune dangling states in DB upon start up (#4697) 2020-01-31 23:15:35 +00: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 Make E2E more consistent, change log file setup (#4696) 2020-01-31 00:16:36 +00:00
minimal_e2e_test.go Replace no-genesis-delay with custom-genesis-delay (#4678) 2020-01-28 21:07:43 +00:00
README.md Allow easy plugin of featureflags into E2E (#4659) 2020-01-26 21:42:10 -05:00
validator.go Prune dangling states in DB upon start up (#4697) 2020-01-31 23:15:35 +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 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