Testing
Forge is a command-line tool that ships with Foundry. Forge tests, builds, and deploys your smart contracts.
Last updated
Forge is a command-line tool that ships with Foundry. Forge tests, builds, and deploys your smart contracts.
Last updated
Testing in Solidity is different from other frameworks like brownie.
Tests are written in in Solidity -> If the test function reverts, the test fails, otherwise it passes.
Essentially we are writing a separate contract containing test functions.
Test contracts end with .t.sol
Usually, tests will be placed in src/test
(or ./test
in windows)
0xb4c79daB8f259C7Aee6E5b2Aa729821864227e84
. If you deploy a contract within your test, then 0xb4c...7e84
will be its deployer.
If the contract deployed within a test gives special permissions to its deployer, such as Ownable.sol
's onlyOwner
modifier, then the test contract 0xb4c...7e84
will have those permissions.
Forge can run your tests with the command.
Forge will look for the tests anywhere in your source directory.
Any contract with a function that starts with test
is considered to be a test.
Running a specific test function
forge test --match-contract ComplicatedContractTest --match-test testDeposit
run the tests in the test contract ComplicatedContractTest
with testDeposit
in the function name.
import the contract to be tested (import 'src/SimpleNameRegister.sol';)
deploy it via factory pattern
The setup function is invoked before each test case is run:
serves to setup the necessary variables and conditions for your test functions to operate.
here we use it to deploy a fresh instance of SimpleNameRegister.sol before each test case is ran via simpleNameRegister = new SimpleNameRegister()
create storage string variable test and assign it "what"
The first function testRegisterDepends() registers ownership of name "what".
Then we call testRelinquishDepends() to check if we can relinquish ownership.
testRelinquishDepends() fails, indicating that the effects from testRegisterDepends() do not spill into testRelinquishDepends().
Since setUp() is invoked before each test case -> each test function interacts with a seperate instance of SimpleNameRegister.sol
manipulate the state of the blockchain -> change block number
change your identity
test for specific reverts and events.
Cheatcodes are functions on contract at address: 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D
To execute a cheatcode function, we need to interface with this contract from our test contract.
Therefore in our test contract we need to do 3 things:
import interface Cheatcodes{} (or just copypasta the interface above your contract like below)
declare interface object as state variable
assignment of state variable: pass the cheatcode contract address into the interface object
prank
: changes the next call's msg.sender to the input address.
This allows us to modify msg.sender in between function calls.
stopPrank
expectRevert
We can do so using expectRevert(bytes calldata)
; it will expect a revert to occur on the next call.
insert it before making a function call that is expected to fail/revert
if the next call does not revert, then expectRevert
will.
After calling expectRevert
, calls to other cheatcodes before the reverting call are ignored.
For require statements, provide the error string as defined in the require:
Reference:
Sets msg.sender
for all subsequent calls until is called.
Stops , resetting msg.sender
and tx.origin
to the values before startPrank
was called.