Back to catalog / Developer tools
Web3 contract testing: verify state invariants and failure boundaries
Use an isolated EVM to test contract state, roles, reverts, and known attack boundaries.
Skills
Identify Foundry or Hardhat and inspect compiler, test config, and deploy scripts without running mainnet scripts. Encode business rules as assertions/invariants. Cover happy paths, boundaries, access denial, reverts, and reentrancy; add fuzz/property tests for variable states. For forks, pin block height, use a read-only RPC, disable signers, and verify no test can broadcast to a real chain. Run the local suite and report test counts, uncovered paths, and reproductions; Before deployment, review differences between the pinned fork and current chain state.
Permissions
Prerequisites
- For unit, integration, fuzz, and fork testing of Solidity/EVM contracts.
- Needs source contracts, build config, invariants, and a controlled test chain.
Permissions
- May edit tests, run a local chain, and deploy test contracts; a fork may access a public RPC.
- Use isolated local/testnet transactions only; no funded production keys or mainnet transactions.
Limitations
Cover invariants, numeric boundaries, reverts, roles, and reentrancy; pin fork blocks and protect credentials.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/blockchain-web3/skills/web3-testing/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Foundry/Hardhat test runner · Local EVM · Mainnet fork without signing keys
Main topic
Take a coding Agent change from context to verification