Open marioevz opened 7 months ago
Basic example of the test filler: https://github.com/ethereum/execution-spec-tests/blob/760a67e03baa23d782c9c8762c13ca6089920bda/tests/prague/eip3540_evm_object_format_v1/test_eof.py#L19
This is not how all tests should be rewritten as this example barely takes any advantage of parameterization, but it's simply an example of usage of the EOFTest
spec class.
To summarize the current status of our existing tests:
https://github.com/ethereum/tests/tree/develop/src/EIPTestsFiller/StateTests/stEOF/stEIP3540 https://github.com/ethereum/tests/tree/develop/src/EIPTestsFiller/StateTests/stEOF/stEIP4200 https://github.com/ethereum/tests/tree/develop/src/EIPTestsFiller/StateTests/stEOF/stEIP4750 https://github.com/ethereum/tests/tree/develop/src/EIPTestsFiller/StateTests/stEOF/stEIP5450
EOF validation tests https://github.com/ethereum/tests/tree/develop/src/EOFTestsFiller
EIP*
folders, also efExample
and ori
), and partially generated from evmone unit tests, which @winsvega merged recently as Copier tests (rest of ef*
folders). I expect these tests to cover almost all aspects of validation reasonably well.https://github.com/ethereum/tests/pull/1324
EOFCREATE
, TXCREATE
, InitcodeTransactions), new EXTCALL*
instructions and some related execution aspects. See also the list at https://github.com/ipsilon/eof/blob/main/spec/implementation_matrix.md#column-descriptions we try to keep it up to date.