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
if you run mud-gas-report on a thing that extends MudTest, it'll fail because it's missing a .mudtest file (created on MUD deploy)
since our deploy pipeline is separate (a TS script) from the rest of the foundry lifecycle, I think we should:
make gas-report (or sub command of) more of a pure "test output parser" rather than a "test runner"
allow overriding the test command used in the gas-report test runner
another wild idea: get MudTest to call out to TS deploy script during the test run, but not sure if there's an exposed RPC within the test runner we can thread through to the deploy process via CLI arg
The text was updated successfully, but these errors were encountered:
if you run
mud-gas-report
on a thing that extendsMudTest
, it'll fail because it's missing a.mudtest
file (created on MUD deploy)since our deploy pipeline is separate (a TS script) from the rest of the foundry lifecycle, I think we should:
another wild idea: get
MudTest
to call out to TS deploy script during the test run, but not sure if there's an exposed RPC within the test runner we can thread through to the deploy process via CLI argThe text was updated successfully, but these errors were encountered: