84e51a5236
* Progress on metrics tests * Progress on metrics test * Get metrics E2E working * Merge branch 'master' of https://github.com/prysmaticlabs/prysm into e2e-metrics * Complete most of metrics tests * Change E2E polling to the middle of a slot, instead of at the start of the middle * Add metrics to all E2E * Remove extra types * Update endtoend/evaluators/metrics.go Co-Authored-By: Preston Van Loon <preston@prysmaticlabs.com> * Merge branch 'master' into e2e-metrics * Add more comments, address feedback * Merge branch 'e2e-metrics' of https://github.com/prysmaticlabs/prysm into e2e-metrics * Fix build * Remove unneeded comment * Set E2E_EPOCHS back * Improve sync testing reliability * Remove metrics check from slashing * Improve time allotted to sync * Remove possibly flaky sync test change |
||
|---|---|---|
| .. | ||
| components | ||
| evaluators | ||
| helpers | ||
| params | ||
| types | ||
| BUILD.bazel | ||
| endtoend_test.go | ||
| long_minimal_e2e_test.go | ||
| minimal_antiflake_e2e_1_test.go | ||
| minimal_antiflake_e2e_2_test.go | ||
| minimal_e2e_test.go | ||
| minimal_slashing_e2e_test.go | ||
| 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
Mainnet Config - 2 beacon nodes, 16,384 validators, running for 5 epochsDisabled 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