crytic / crytic/echidna

[Bug-Candidate]: Fix coverage report

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

Description

### Describe the issue:

Unclear how to read the coverage report when there is no additional information from Echidna on the state of these properties.

As an example, for the following screenshot, I'm not sure how to interpret this. What happened on the USDC.borrow for it to never be hit, but the DAI borrow could occur?

![cov-output-echidna](https://github.com/crytic/echidna/assets/16736724/fc776194-9c26-497d-9e2e-73c48ce57e87)

On the flip side, how should I interpret the following? The fuzzer never showed me an assertion failure on this property, so my intuition is that it should be successful (therefore all statements running green)? - yet the `assertWithMsg` is showing up as red.
![additional-cov-output](https://github.com/crytic/echidna/assets/16736724/bd1edc00-1d0b-455f-9337-eb315819e504)

### Code example to reproduce the issue:

[Curvance](https://github.com/curvance/Curvance-CantinaCompetition/tree/CodeFAQAndAdjustments) :)

### Version:

Echidna 2.2.3

### Relevant log output:

_No response_

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.