Filling Tests for Features under Development¶
Requirements¶
By default, execution-spec-tests only generates fixtures for forks that have been deployed to mainnet. In order to generate fixtures for evm features that are actively under development:
- A version of the
evm
andsolc
tools that implement the feature must be available (although, typically only a developer version of theevm
tool is required, usually the latest stable release ofsolc
is adequate), and, -
The development fork to test must be explicitly specified on the command-line:
fill -k 4844 --fork=Cancun -v
fill -k 4844 --from=Cancun -v
fill -k 4844 --until=Cancun -v
Specifying the evm
binary via evm-bin
It is possible to explicitly specify the evm
binary used to generate fixtures via the --evm-bin
flag, for example,
fill --fork=Cancun --evm-bin=/opt/bin/evm -v
Further Help¶
Verifying evm
and solc
versions used
The versions used to generate fixtures are displayed in the console output:
VS Code Setup¶
By default, VS Code's Testing View will only show tests for stable forks. To show tests for development forks, uncomment the relevant line in the python.testing.pytestArgs
configuration section of included settings file (.vscode/settings.json
) to enable the --until=FORK
flag. See VS Code Setup for help finding the settings files.