You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If there's ever a breaking change to the TOML spec, we have to update all the builtin scenarios. Running them in CI will make sure we don't miss any, and will also alert us if we don't realize we've made a breaking change.
Describe the solution you'd like
Add a rust test that loads the scenario configs from the files in ./scenarios/ and runs setup and a short spam run on a spawned anvil instance.
Describe alternatives you've considered
I considered writing a shell script that would invoke the CLI, but that would be kind of muddy, because now we'd be testing both the CLI and the scenario files. This test only needs to consider whether the scenario files are valid, both syntactically and functionally.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If there's ever a breaking change to the TOML spec, we have to update all the builtin scenarios. Running them in CI will make sure we don't miss any, and will also alert us if we don't realize we've made a breaking change.
Describe the solution you'd like
Add a rust test that loads the scenario configs from the files in ./scenarios/ and runs
setup
and a shortspam
run on a spawned anvil instance.Describe alternatives you've considered
I considered writing a shell script that would invoke the CLI, but that would be kind of muddy, because now we'd be testing both the CLI and the scenario files. This test only needs to consider whether the scenario files are valid, both syntactically and functionally.
The text was updated successfully, but these errors were encountered: