Shipping Reliable Smart Contracts: A Testing Checklist
F
Fatima Al-Rashid
Jul 30, 2026 · 1 min read · 1 comment
Smart contracts are unforgiving: there is no hotfix after deployment. This is the checklist we run before mainnet.
Before writing tests
- Write down every invariant ("total supply never changes", "only the owner can pause").
- List every external call.
Tests
- Unit tests for every public function, including failure paths.
- Fuzz tests for arithmetic and access control.
- Fork tests against real mainnet state for integrations.
Before deploy
- Static analysis with no unexplained findings.
- A second engineer reviews the diff line by line.
- A staged rollout with caps on value at risk.
Checklists are boring. Exploits are worse.
6
Like
1
Insightful
1
Fire
Sign in to react and save
Discussion (1)
Sign in to join the discussion.
Seun Afolabi ·
I'd add invariant testing with Foundry to step 2. It finds things unit tests never will.