Invariant Testing

[gakonst]

@transmissions11 leaked some alpha by @MrChico from the dapphub chat

This algorithm should be easy to do inside our fuzzer logic.

you should run the invariant func once before you do any txs
Because sometimes it doesn’t hold off the bat but then that changes after txs or if all the txs revert then the invariant will show as passed when it may have totally failed if ever called
dapphub/dapptools#745

[transmissions11]

personal wishlist:

1. would like a way to specify that a test can revert, just not fail an assert
2. would like to fuzz a set of invariants for time instead of fixed fuzz runs, or as long as i want
   a) ui showing failures as they occur and the progress of the campaign
   b) don't stop the campaign after a failure is found, keep fuzzing parts of it if possible
3. would like a way to control the list of accounts that the fuzzer calls things from
4. would like a way to control the contracts the fuzzer targets

[lucas-manuel]

Working on invariants right now so will come back with a wish list as well, is this currently being worked on btw?

[gakonst]

I think @brockelmore had hacked something?

[brockelmore]

no that was just in solidity didnt impl in foundry

[lucas-manuel]

One thing that would be really nice is a summary of how many times each function was called and the mean values like in the current fuzz run output. Also logging numbers of reversions for each function call if any.

[mattsse]

vote close @joshieDo

[gakonst]

would like a way to control the list of accounts that the fuzzer calls things from

I think we don't have this yet? Probably for separate issue.

[joshieDo]

We do with targetSenders and excludeSenders.

So feel free to close!