test_worst_calldataload()

Documentation for tests/benchmark/test_worst_compute.py::test_worst_calldataload@88e9fb8f.

Generate fixtures for these test cases for Osaka with:

fill -v tests/benchmark/test_worst_compute.py::test_worst_calldataload -m benchmark

Test running a block with as many CALLDATALOAD as possible.

Source code in tests/benchmark/test_worst_compute.py

@pytest.mark.parametrize(
    "calldata",
    [
        pytest.param(b"", id="empty"),
        pytest.param(b"\x00", id="zero-loop"),
        pytest.param(b"\x00" * 31 + b"\x20", id="one-loop"),
    ],
)
def test_worst_calldataload(
    benchmark_test: BenchmarkTestFiller,
    calldata: bytes,
) -> None:
    """Test running a block with as many CALLDATALOAD as possible."""
    benchmark_test(
        code_generator=JumpLoopGenerator(
            setup=Op.PUSH0,
            attack_block=Op.CALLDATALOAD,
            tx_kwargs={"data": calldata},
        ),
    )

Parametrized Test Cases

This test case is only parametrized by fork.

Fork All Forks Prague Osaka

Fixture Type All Fixture Types blockchain_test

Test ID (Abbreviated)	calldata
...fork_Prague-blockchain_test-empty
...fork_Prague-blockchain_test-zero-loop	00
...fork_Prague-blockchain_test-one-loop	00000000000000000000000000000000 00000000000000000000000000000020
...fork_Osaka-blockchain_test-empty
...fork_Osaka-blockchain_test-zero-loop	00
...fork_Osaka-blockchain_test-one-loop	00000000000000000000000000000000 00000000000000000000000000000020