The tool should parse the EVM contract JSON and learn how many arguments the constructor accepts. For example:
{
"type": "constructor",
"inputs": [
{
"name": "tokenName",
"type": "string",
"internalType": "string"
},
{
"name": "decimals_",
"type": "uint8",
"internalType": "uint8"
},
{
"name": "minAmount_",
"type": "uint256",
"internalType": "uint256"
}
],
"stateMutability": "nonpayable"
}
In this case, the generated test setup code should put three todo!() in the deploy() call.
The tool should parse the EVM contract JSON and learn how many arguments the constructor accepts. For example:
{ "type": "constructor", "inputs": [ { "name": "tokenName", "type": "string", "internalType": "string" }, { "name": "decimals_", "type": "uint8", "internalType": "uint8" }, { "name": "minAmount_", "type": "uint256", "internalType": "uint256" } ], "stateMutability": "nonpayable" }In this case, the generated test setup code should put three
todo!()in thedeploy()call.