Component

Forge

Describe the feature you would like

Aggregating a list of new cheatcodes and improvements to existing cheatcodes that have been requested in other issues:

• 1. vm.not cheat code. When called immediately before (or after?) expectEmit or expectCall it modifies that cheat code so the event/call is expected not to be present. Alternatively, expectNoEmit or expectNoCall would work. https://github.com/gakonst/foundry/issues/509
• 2. Allow expectEmit to be declared after the call emitting the event, instead of the current workflow which requires it to be declared before. If we have to choose only allowing it to be declared before or after, my preference would be after, because it allows you to read updated state from the call and use those values as the event args, as explained in https://github.com/gakonst/foundry/issues/512#issuecomment-1016577046
• 3. Update mockCall, expectCall, and expectRevert (and expectEmit?) to work for JUMPs (currently they only work for calls). This has been discussed in bug: mockCall not working as expected #432 and expectRevert cheat code doesn't work for internal calls #864
• 4. When an expectEmit matcher fails, specify which topics or data did not match: https://github.com/gakonst/foundry/issues/592
• 5. Some expectEmit issues described in https://github.com/gakonst/foundry/issues/760
• 6. Still needs more discussion to determine if cheatcodes is the optimal approach, but I think cheatcodes for setting fuzzer params on a per-contract or per-test basis would be very useful: https://github.com/gakonst/foundry/issues/744
• 7. Nonce cheatcodes: https://github.com/gakonst/foundry/issues/554
• 8. captureLogs and getLogs cheatcodes (similar to records and accesses) to support https://github.com/gakonst/foundry/issues/543
• 9. vm.roll should update how RPC queries behave when forking: https://github.com/gakonst/foundry/issues/939
• 10. expectEmit error message: https://github.com/gakonst/foundry/issues/908
• 11. expectRevert with no bytes to assert that any revert should happen: https://github.com/gakonst/foundry/issues/885
• 12. Needs discussion/decision, but requiring expectEmit/expectCall to only check the next call, and not all subsequent calls: bug: expectEmit and expectCall don't only check the next call #1745
• 13. Some expect* edge cases / bugs? Forge doesn't work with multiple "vm.expectRevert" when testing free functions #3723 (comment)

Additional context

No response