Invariant Testing
Invariant testing is a smart contract testing methodology that verifies properties (invariants) that must always hold true, regardless of the sequence of transactions or state changes applied to the system.
In Depth
Invariant testing goes beyond traditional unit tests by defining properties that should never be violated across all possible execution paths. A fuzzer generates random sequences of function calls and checks these invariants after each transaction. If an invariant breaks, the fuzzer reports the exact sequence that caused the violation. This approach is especially powerful for DeFi protocols where accounting correctness, solvency, and access control must hold under all conditions.
Frequently Asked Questions
What is invariant testing in smart contracts?
Invariant testing is a technique where you define properties (invariants) that must always be true in your smart contract system, then use a fuzzer to try millions of random transaction sequences to find violations. For example, 'total deposits must always equal total shares times price per share' is an invariant.
How is invariant testing different from unit testing?
Unit tests check specific scenarios you can think of. Invariant testing checks properties across millions of randomly generated scenarios, finding edge cases humans miss. Unit tests answer 'does this specific input produce this output?' while invariant tests answer 'does this property hold for ALL possible inputs?'
What tools are used for invariant testing?
The main tools for smart contract invariant testing are Echidna, Medusa, Foundry (forge), and Halmos. Recon's Chimera framework allows writing tests that are compatible with all three fuzzers simultaneously.