23fa8d0c70
`scanf` apparently has both a `bool` return as well as raising random exceptions depending on what functions get called by the `macro`. To make this explicit, catch the `ValueError` from the generated `parseInt` call, to separate `scanf` behaviour from the actual SSZ test logic. In the end, it mostly doesn't matter as there are some `doAssert wasMatched` on the next line (not everywhere though). But it still makes the `scanf` internals explicit, so is clearer. |
||
|---|---|---|
| .. | ||
| altair | ||
| bellatrix | ||
| capella | ||
| deneb | ||
| phase0 | ||
| README.md | ||
| all_tests.nim | ||
| consensus_spec_tests_preset.nim | ||
| fixtures_utils.nim | ||
| os_ops.nim | ||
| test_fixture_fork.nim | ||
| test_fixture_fork_choice.nim | ||
| test_fixture_kzg.nim | ||
| test_fixture_light_client_single_merkle_proof.nim | ||
| test_fixture_light_client_sync.nim | ||
| test_fixture_light_client_update_ranking.nim | ||
| test_fixture_merkle_proof.nim | ||
| test_fixture_sanity_blocks.nim | ||
| test_fixture_sanity_slots.nim | ||
| test_fixture_ssz_generic_types.nim | ||
| test_fixture_transition.nim | ||
README.md
Tests based on scenarios generated from the consensus spec.