-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug information can be insufficient #656
Comments
I would be really interested in the last point If we run echidna to test this method, we won't get much information about the state of the contract when it failed. This information would improve the debugging. |
Hi,
Have something like:
|
You mean, when a property fails, right? |
Yes, when the |
Showing events for all calls in the sequence would really help me out. It is especially useful when using helper functions that modify the value, for example using modulo to get values in a small range. Currently I work around this by storing the modified value by the helper function and logging it in the final call. |
When echidna generates inputs or finds a property failure, it will be nice to have additional information on what Echidna is doing or the state of the contract. Some ideas for this:
The text was updated successfully, but these errors were encountered: