fuzzing

When the computer is suspended during a fuzzing session, the time spent in suspended state is counted as a "run time" on a statistics screen. In case fuzzing was running for several hours and then the computer was suspended for several more hours, on one hand I would prefer not restarting the session, on the other hand, now it may be harder to tell how well a harness performs (corpus count vs. run

Component

Forge

Describe the feature you would like

This was a dumb mistake on my part, but it took me a while to get the proper capitalization of the setUp() function.

It'd be nice if Forge would emit a warning or error when a test contract includes the incorrect of these two sigs:

0a9254e4: setUp() // Right
ba0bba40: setup() // Wrong

Additional context

_No re

Hello everyone,
I think that the boofuzz documentation is good, but somehow not very useful for beginners.
In my opinion, the quickstart section is too short, leaving new users without any guidance on how to use this framework.
So I would suggest adding a whole section with detailed examples, covering at least the current examples,

I wonder if it was considered to add a rewrite step as a MSBuild target in the NuGet package. This way calling the tool coyote rewrite wouldn't be needed as that would be done automatically once the assembly is generated.

Could possibly be done if a specific property is provided like /p:CoyoteRewrite=true or be an opt-out when Configuration=Debug.