Test All Opcodes In Container¶
Documentation for tests/osaka/eip7692_eof_v1/eip3540_eof_v1/test_all_opcodes_in_container.py@49a16fac
.
Generate fixtures for these test cases for Osaka with:
fill -v tests/osaka/eip7692_eof_v1/eip3540_eof_v1/test_all_opcodes_in_container.py --fork Osaka
Test Functions Overview¶
Name | Type | Cases (Osaka) | Description |
---|---|---|---|
test_all_opcodes_in_container |
eof_test | 255 | Test all opcodes inside valid container |
test_invalid_opcodes_after_stop |
eof_test | 624 | Test that an invalid opcode placed after STOP (terminating instruction) invalidates EOF. |
test_all_invalid_terminating_opcodes |
eof_test | 142 | Test all opcodes that are invalid as the last opcode in a container. |
test_all_unreachable_terminating_opcodes_after_stop |
eof_test | 7 | Test all terminating opcodes after stop. |
test_all_unreachable_terminating_opcodes_before_stop |
eof_test | 6 | Test all opcodes terminating opcodes before. |
test_all_opcodes_stack_underflow |
eof_test | 96 | Test stack underflow on all opcodes that require at least one item on the stack. |
test_all_opcodes_stack_overflow |
eof_test | 140 | Test stack overflow on all opcodes that push more items than they pop. |
test_truncated_data_portion_opcodes |
eof_test | 152 | Test that an instruction with data portion and truncated immediate bytes |