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.
This commit is contained in:
Paul Hauner
2019-03-02 18:37:21 +11:00
parent 8e1380d7c4
commit e59404f463
3 changed files with 36 additions and 78 deletions

View File

@@ -20,19 +20,18 @@ test_cases:
amount: 32
merkle_index: 2
proposer_slashings:
- slot: 8 # At slot 8, trigger a proposal slashing
proposer_index: 42 # Penalize the validator at position 42
proposal_1_shard: 0
proposal_1_slot: 15
proposal_1_root: !!binary |
LkmqmqoodLKAslkjdkajsdljasdkajlksjdasldjasdd
proposal_2_shard: 0
proposal_2_slot: 15
proposal_2_root: !!binary |
DIFFERENTKAslkjdkajsdljasdkajlksjdasldjasdd
# At slot 2, trigger a proposer slashing for validator #42.
- slot: 2
validator_index: 42
# At slot 8, trigger a proposer slashing for validator #13.
- slot: 8
validator_index: 13
attester_slashings:
# At slot 2, trigger an attester slashing for validators #11 and #12
# At slot 2, trigger an attester slashing for validators #11 and #12.
- slot: 2
validator_indices: [11, 12]
# At slot 5, trigger an attester slashing for validator #14.
- slot: 5
validator_indices: [14]
results:
num_validators: 1000