node --require esm ./node_modules/.bin/hardhat test --network hardhat
Alternatively, you can run a local Hardhat node in another terminal using
yarn chain --network hardhat
then run the following:
It might happens that Hardhat cannot resolve custom error (test failing on "Expecter nameOfTheError() but reverted without a reason string"), just restart yarn chain.
End-to-end tests have been written in Solidity, using Foundry.
To get set up:
curl -L https://foundry.paradigm.xyz | sh
git submodule update --init
To check current unit tests coverage:
node --require esm ./node_modules/.bin/hardhat coverage --network hardhat
A few notes:
Juicebox uses the Hardhat Deploy plugin to deploy contracts to a given network. But before using it, you must create a
./mnemonic.txt file containing the mnemonic phrase of the wallet used to deploy. You can generate a new mnemonic using this tool. Generate a mnemonic at your own risk.
Then, to execute the
./deploy/deploy.js script, run the following:
npx hardhat deploy --network $network
_You'll likely want to set the optimizer runs to 10000 in
./hardhat.config.js before deploying to prevent contract size errors. The preset value of 1000000 is necessary for hardhat to run unit tests successfully. Bug about this opened here.
Contract artifacts will be outputted to
./deployments/$network/** and should be checked in to the repo.
To verify the contracts on Etherscan, make sure you have an
ETHERSCAN_API_KEY set in your
./.env file. Then run the following:
npx hardhat --network $network etherscan-verify
This will verify all of the deployed contracts in