Web3 & DApp Development Fundamentals · Pelajaran

Menguji Revert dan Event

Memastikan perilaku

Menguji Revert dan Event 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.

Reverts and Events

Beyond return values, contracts communicate through reverts (transactions that fail and undo state) and events (logs emitted on success).

Good tests assert both: that valid actions emit the right events, and that invalid actions revert with the right reason.

Hardhat Chai Matchers

The Toolbox adds special Chai matchers for Ethereum, available after importing them (the Toolbox does this automatically):

.to.be.revertedWith(...)
.to.be.revertedWithCustomError(...)
.to.emit(...)
.to.changeEtherBalance(...)

Asserting a Revert

To check that a transaction fails, wrap the call (without awaiting it first) and use revertedWith:

await expect(
  token.connect(alice).withdraw()
).to.be.revertedWith("Not the owner");

The string must match the contract's require message exactly.

await expect(
  token.connect(alice).withdraw()
).to.be.revertedWith("Not the owner");

Custom Error Reverts

Modern Solidity uses gas-efficient custom errors. Assert them with revertedWithCustomError:

await expect(
  vault.connect(alice).withdraw()
).to.be.revertedWithCustomError(vault, "Unauthorized");

You pass the contract instance so the matcher can decode the error from the ABI.

await expect(
  vault.connect(alice).withdraw()
).to.be.revertedWithCustomError(vault, "Unauthorized");

Checking Error Arguments

Custom errors can carry data. Chain withArgs to assert the values:

await expect(
  vault.withdraw(amount)
).to.be.revertedWithCustomError(vault, "InsufficientBalance")
  .withArgs(amount, balance);

This verifies the contract reverted for the exact reason you expect.

await expect(
  vault.withdraw(amount)
).to.be.revertedWithCustomError(vault, "InsufficientBalance")
  .withArgs(amount, balance);

Asserting an Event

Use .to.emit to assert that a transaction emitted an event:

await expect(token.transfer(bob.address, 100))
  .to.emit(token, "Transfer");

You pass the contract and the event name. This confirms the log was produced.

await expect(token.transfer(bob.address, 100))
  .to.emit(token, "Transfer");

Checking Event Arguments

Combine emit with withArgs to verify the event payload:

await expect(token.transfer(bob.address, 100))
  .to.emit(token, "Transfer")
  .withArgs(owner.address, bob.address, 100);

This ensures the from, to, and amount fields are exactly correct.

await expect(token.transfer(bob.address, 100))
  .to.emit(token, "Transfer")
  .withArgs(owner.address, bob.address, 100);

Checking Balance Changes

For ETH transfers, changeEtherBalance asserts the net change for an account:

await expect(
  () => vault.connect(alice).withdraw()
).to.changeEtherBalance(alice, ethers.parseEther("1"));

There is also changeTokenBalance for ERC-20 transfers.

await expect(
  () => vault.connect(alice).withdraw()
).to.changeEtherBalance(alice, ethers.parseEther("1"));

Reverts Without a Reason

Some failures have no message — for example, arithmetic underflow panics or plain revert(). Assert these generically:

await expect(token.transfer(bob.address, 999999))
  .to.be.reverted;

For panic codes specifically, use revertedWithPanic.

await expect(token.transfer(bob.address, 999999))
  .to.be.reverted;

Why This Matters

Testing reverts and events covers the negative and observable paths of your contract:

Reverts prove your guards (access control, balance checks) actually block bad input.
Events prove off-chain systems will receive the right notifications.

Skipping these leaves dangerous gaps in coverage.

Asserting State Did Not Change

After a revert, it is good practice to confirm state was untouched, since reverts roll back all changes:

await expect(
  vault.connect(alice).withdraw()
).to.be.revertedWithCustomError(vault, "Unauthorized");

expect(await vault.balance()).to.equal(initial);

This double-checks the guard truly protected the state.

await expect(
  vault.connect(alice).withdraw()
).to.be.revertedWithCustomError(vault, "Unauthorized");

expect(await vault.balance()).to.equal(initial);

Quick Check

Test your understanding of revert and event assertions.

Recap

You learned to assert behavior beyond return values.

revertedWith checks require messages; revertedWithCustomError checks custom errors.
withArgs verifies error or event arguments precisely.
.to.emit confirms events fired.
changeEtherBalance / changeTokenBalance assert net balance changes.
Use .to.be.reverted for failures without a reason string.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Menguji Revert dan Event” gratis?

Ya — teks lengkap “Menguji Revert dan Event” 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 “Menguji Revert dan Event”?

Memastikan perilaku 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 “Menguji Revert dan Event” 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

← Kembali ke Web3 & DApp Development Fundamentals