crytic / crytic/echidna

Feature Request: Add setting to consider reverted tests as failed in assertion mode

Open
#1,248 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Haskell
Stars
3.2k
Forks
432
Avg merge
1d 20h
Merged PRs (30d)
5

Description

### Describe the desired feature

I have switched to writing all my tests so that they should never revert. Currently I'm using additional self-tests to check my tests for unwanted reverts, it would be nice if this is a built-in option in Echidna.

Medusa has something similar:
```json
"panicCodeConfig": {
"failOnCompilerInsertedPanic": false,
"failOnAssertion": true,
"failOnArithmeticUnderflow": false,
"failOnDivideByZero": false,
"failOnEnumTypeConversionOutOfBounds": false,
"failOnIncorrectStorageAccess": false,
"failOnPopEmptyArray": false,
"failOnOutOfBoundsArrayAccess": false,
"failOnAllocateTooMuchMemory": false,
"failOnCallUninitializedVariable": false
}
```

For my use case it would be enough to consider **any** revert as a failed test

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.