Pengujian forge
Pengujian Solidity
Pengujian forge adalah pelajaran Web3 & DApp Development Fundamentals gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Web3 & DApp Development Fundamentals, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Web3 & DApp Development Fundamentals mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Tests Are Contracts
In Foundry a test file is a Solidity contract that inherits from Test in the forge-std library. Each public function whose name starts with test is run as an individual test case.
Test files live in test/ and conventionally use the .t.sol suffix.
import {Test} from "forge-std/Test.sol";
contract CounterTest is Test {
function testInitialZero() public {
// ...
}
}The setUp Function
The special setUp() function runs before every test, giving each test a fresh, isolated state. Deploy your contracts and seed any fixtures here.
Because state resets between tests, one test can never accidentally depend on another.
Counter counter;
function setUp() public {
counter = new Counter();
}Assertions
forge-std provides assertion helpers that fail the test with a clear message when they do not hold:
assertEq(a, b)— equalityassertTrue(cond)/assertFalse(cond)assertGt,assertLt,assertGe,assertLe
function testIncrement() public {
counter.increment();
assertEq(counter.number(), 1);
}Running Tests
Run the whole suite with forge test. Filter by name with --match-test or by contract with --match-contract. Increase verbosity with -v flags to see logs and traces.
$ forge test
$ forge test --match-test testIncrement -vvvExpecting Reverts
Use vm.expectRevert immediately before a call that should fail. The test passes only if the next call reverts, optionally matching a specific error message or custom error.
function testOnlyOwner() public {
vm.prank(address(0xBEEF));
vm.expectRevert("not owner");
counter.adminReset();
}Impersonating Accounts
vm.prank(addr) sets msg.sender for the very next call. vm.startPrank(addr) applies it to all calls until vm.stopPrank(). This lets you test access control without deploying from many keys.
vm.startPrank(alice);
token.approve(spender, 100);
token.transfer(bob, 50);
vm.stopPrank();Manipulating Balances and Time
Cheatcodes let you control the environment:
vm.deal(addr, amount)— set an account's ETH balancevm.warp(timestamp)— set block.timestampvm.roll(blockNum)— set block.number
These make time-dependent and balance-dependent logic easy to test deterministically.
vm.deal(alice, 10 ether);
vm.warp(block.timestamp + 7 days);
vm.roll(block.number + 100);Testing Events
vm.expectEmit declares which event fields to check, followed by the expected event, then the call that should emit it. The booleans select which topics and data to match.
vm.expectEmit(true, true, false, true);
emit Transfer(alice, bob, 100);
token.transfer(bob, 100);Labels and Logs
vm.label(addr, name) gives addresses readable names in traces. console.log from forge-std prints debug output during tests when run with sufficient verbosity.
import {console} from "forge-std/console.sol";
vm.label(alice, "Alice");
console.log("balance:", token.balanceOf(alice));Fork Testing
Foundry can fork a live network so your tests run against real deployed contracts and state. Set an RPC URL and use vm.createSelectFork to pin a block.
This is invaluable for testing integrations with protocols like Uniswap or Aave without redeploying them.
function setUp() public {
vm.createSelectFork(vm.rpcUrl("mainnet"), 19000000);
}Test Organization
Good practices for forge tests:
- One behavior per test function
- Descriptive names like
testRevertWhenNotOwner - Shared setup in
setUp() - Use prank for access control, warp for time logic
- Add fork tests for external integrations
Quick Check
What is the purpose of the setUp() function in a Foundry test contract?
Recap
You learned forge testing:
- Tests are Solidity contracts inheriting
Test; functions start withtest setUp()gives fresh state per test- Assertions:
assertEq,assertTrue, etc. - Cheatcodes:
prank,deal,warp,expectRevert,expectEmit - Fork tests run against live network state
Next: fuzzing and invariant testing.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pengujian forge” gratis?
Ya — teks lengkap “Pengujian forge” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Web3 & DApp Development Fundamentals, upgrade ke CoddyKit PRO. Kursus Web3 & DApp Development Fundamentals mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pengujian forge”?
Pengujian Solidity Kamu berlatih Web3 & DApp Development Fundamentals dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Web3 & DApp Development Fundamentals?
Tidak diperlukan pengalaman sebelumnya. Web3 & DApp Development Fundamentals di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.
Berapa lama pelajaran “Pengujian forge” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Web3 & DApp Development Fundamentals ini?
Ya. Setiap pelajaran Web3 & DApp Development Fundamentals menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Foundry vs Hardhat
- Pengujian forge
- Fuzzing dan Invarian
- cast dan anvil