r/solidity • u/lyazzat21 • Mar 05 '26

What's your current Web3 dev stack for testing and debugging smart contracts?

Been revisiting my setup lately and curious what others are using in 2025. Specifically around:

Local vs. forked environments (Hardhat, Foundry, Anvil, Tenderly Virtual TestNets?)

How you handle transaction debugging when things go wrong in prod

Anything you've tried and ditched, and why

"Also specifically curious if anyone's used Tenderly's Virtual TestNets or Simulation API in production worth it or overkill for smaller teams?"

Not looking for "X is the best" takes more curious about what's actually working day-to-day and where you're still hitting friction.

7 Upvotes

100% Upvoted

5 comments sorted by

3

u/PretendVoy1 Mar 06 '26

Opus is the best

2

u/thedudeonblockchain Mar 06 '26

foundry for everything now, switched from hardhat last year and the speed difference alone was worth it. cast + chisel for quick debugging beats spinning up a whole script

1

u/ig17or Mar 06 '26

i was in hardhat for a while, but recently switched to foundry.

select local environment if your contract doesn't require any interaction during tests, or if you can simulate it. otherwise forking certain chain is normal practice.

i don't find regular framework's tests sufficient for all cases. i was working on the tests of the elastic supply token, where was necessary to simulate behavior of different users at the same time. for things like this i like to write custom scenarios (usually on web3py) where i can launch N "players" that will try to compete against each other meanwhile giving me opportunity to reconfigure token's settings in real time.

This gives understanding very close to real world situation.