lighthouse/beacon_node/beacon_chain/test_harness/examples/chain.yaml

title: Validator Registry Tests
summary: Tests deposit and slashing effects on validator registry.
test_suite: validator_registry
fork: tchaikovsky
version: 1.0
test_cases:
  - config:
      epoch_length: 64
      deposits_for_chain_start: 1000
      num_slots: 64
      skip_slots: [2, 3]
      deposits:
          # At slot 1, create a new validator deposit of 32 ETH.
        - slot: 1
          amount: 32
          # Trigger more deposits...
        - slot: 3
          amount: 32
        - slot: 5
          amount: 32
      proposer_slashings:
          # At slot 2, trigger a proposer slashing for validator #42.
        - slot: 2
          validator_index: 42
          # Trigger another slashing...
        - slot: 8
          validator_index: 13
      attester_slashings:
          # At slot 2, trigger an attester slashing for validators #11 and #12.
        - slot: 2
          validator_indices: [11, 12]
          # Trigger another slashing...
        - slot: 5
          validator_indices: [14]
    results:
      num_skipped_slots: 2
      states:
        - slot: 63
          num_validators: 1003
          slashed_validators: [11, 12, 13, 14, 42]
          exited_validators: []
Update test_harness yaml - Checks for attester slashing, now it is included in the chain. - Renames suite to be more specific, use normal Eth2.0 naming 2019-03-03 00:19:27 +00:00			`title: Validator Registry Tests`
			`summary: Tests deposit and slashing effects on validator registry.`
			`test_suite: validator_registry`
			`fork: tchaikovsky`
Add basic YAML test_harness tests Works, however ignores a lot of fields in the YAML. 2019-02-28 12:13:00 +00:00			`version: 1.0`
			`test_cases:`
			`- config:`
			`epoch_length: 64`
			`deposits_for_chain_start: 1000`
Add state-checks to test_harness YAML Runs tests against a state at some slot 2019-03-02 09:17:14 +00:00			`num_slots: 64`
Add skip_slots to test_harness yaml processor 2019-03-01 02:28:07 +00:00			`skip_slots: [2, 3]`
Add support for deposits to test_harness 2019-03-01 05:59:55 +00:00			`deposits:`
Remove merkle_index from test_harness YAML IMO, this is an implementation detail that shouldn't be covered in these tests. 2019-03-03 00:31:08 +00:00			`# At slot 1, create a new validator deposit of 32 ETH.`
Add support for deposits to test_harness 2019-03-01 05:59:55 +00:00			`- slot: 1`
			`amount: 32`
Remove merkle_index from test_harness YAML IMO, this is an implementation detail that shouldn't be covered in these tests. 2019-03-03 00:31:08 +00:00			`# Trigger more deposits...`
Add support for deposits to test_harness 2019-03-01 05:59:55 +00:00			`- slot: 3`
			`amount: 32`
			`- slot: 5`
			`amount: 32`
Add proposer slashing support to test_harness Test harness will now add signatures to a ProposerSlashing and submit it to the BeaconChain 2019-03-02 00:25:55 +00:00			`proposer_slashings:`
Change test_harness proposer_slashings YAML Removes a lot of the detail from the `proposer_slashings` field -- IMO this is not necessary in the test spec, the details of how a proposer_slashing is created should be held in the program and the spec should only define that one happens. 2019-03-02 07:37:21 +00:00			`# At slot 2, trigger a proposer slashing for validator #42.`
			`- slot: 2`
			`validator_index: 42`
Remove merkle_index from test_harness YAML IMO, this is an implementation detail that shouldn't be covered in these tests. 2019-03-03 00:31:08 +00:00			`# Trigger another slashing...`
Change test_harness proposer_slashings YAML Removes a lot of the detail from the `proposer_slashings` field -- IMO this is not necessary in the test spec, the details of how a proposer_slashing is created should be held in the program and the spec should only define that one happens. 2019-03-02 07:37:21 +00:00			`- slot: 8`
			`validator_index: 13`
Add basic YAML test_harness tests Works, however ignores a lot of fields in the YAML. 2019-02-28 12:13:00 +00:00			`attester_slashings:`
Change test_harness proposer_slashings YAML Removes a lot of the detail from the `proposer_slashings` field -- IMO this is not necessary in the test spec, the details of how a proposer_slashing is created should be held in the program and the spec should only define that one happens. 2019-03-02 07:37:21 +00:00			`# At slot 2, trigger an attester slashing for validators #11 and #12.`
Shorten test_harness YAML to single test 2019-03-02 04:28:01 +00:00			`- slot: 2`
			`validator_indices: [11, 12]`
Remove merkle_index from test_harness YAML IMO, this is an implementation detail that shouldn't be covered in these tests. 2019-03-03 00:31:08 +00:00			`# Trigger another slashing...`
Change test_harness proposer_slashings YAML Removes a lot of the detail from the `proposer_slashings` field -- IMO this is not necessary in the test spec, the details of how a proposer_slashing is created should be held in the program and the spec should only define that one happens. 2019-03-02 07:37:21 +00:00			`- slot: 5`
			`validator_indices: [14]`
Add basic YAML test_harness tests Works, however ignores a lot of fields in the YAML. 2019-02-28 12:13:00 +00:00			`results:`
Add state-checks to test_harness YAML Runs tests against a state at some slot 2019-03-02 09:17:14 +00:00			`num_skipped_slots: 2`
			`states:`
			`- slot: 63`
			`num_validators: 1003`
Update test_harness yaml - Checks for attester slashing, now it is included in the chain. - Renames suite to be more specific, use normal Eth2.0 naming 2019-03-03 00:19:27 +00:00			`slashed_validators: [11, 12, 13, 14, 42]`
Add state-checks to test_harness YAML Runs tests against a state at some slot 2019-03-02 09:17:14 +00:00			`exited_validators: []`