71a6c73e93
* fully remove kad * Merge branch 'master' into rem-kad * Update beacon-chain/p2p/service.go * no workspace kad * Merge branch 'rem-kad' of github.com:prysmaticlabs/prysm into rem-kad * mod tidy * Merge refs/heads/master into rem-kad * Merge refs/heads/master into rem-kad * Merge refs/heads/master into rem-kad * add back bootnode query tool * Merge branch 'rem-kad' of github.com:prysmaticlabs/prysm into rem-kad * fix up multiaddr tests * fix build * fix up go build * fix go build * update dep * Merge refs/heads/master into rem-kad * Merge refs/heads/master into rem-kad * Merge refs/heads/master into rem-kad * Merge refs/heads/master into rem-kad |
||
|---|---|---|
| .. | ||
| components | ||
| evaluators | ||
| helpers | ||
| params | ||
| types | ||
| BUILD.bazel | ||
| endtoend_test.go | ||
| geth_deps.go | ||
| long_minimal_e2e_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 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 - 2 beacon nodes, 256 validators, running for 8 epochs
- Minimal Config Slashing Test - 2 beacon nodes, 256 validators, tests attester and proposer slashing
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