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
While using Hardhat Ignition modules with hardhat fixtures in tests, I'm facing a problem. When using hardhat network and repeatedly executing hardhat test test/myTest.ts I get many errors in console, linked to the fact that I'm running the test for the second time - the state of the contracts is altered by the first test run.
Maybe consider adding something like hardhat ignition wipe deploymentId * so that at least it is possible to delete entire deployment via console.
Or perhaps —reset flag on hardhat test would be handy.
Search terms
hardhat ignition test hardhat network
The text was updated successfully, but these errors were encountered:
Are the tests you are running against an external hardhat node during tests, is that why you are seeing deployments created in the deployment folder?
We recently added a capacity to explicitly write to the deployment folder: #816 @zoeyTM does the opposite also work, can you set it to never write to the deployment folder even in a test against a local Hardhat node?
Describe the feature
While using Hardhat Ignition modules with hardhat fixtures in tests, I'm facing a problem. When using hardhat network and repeatedly executing
hardhat test test/myTest.ts
I get many errors in console, linked to the fact that I'm running the test for the second time - the state of the contracts is altered by the first test run.Maybe consider adding something like
hardhat ignition wipe deploymentId *
so that at least it is possible to delete entire deployment via console.Or perhaps
—reset
flag onhardhat test
would be handy.Search terms
hardhat ignition test hardhat network
The text was updated successfully, but these errors were encountered: