crytic/echidna

Expression-level coverage support

Open

#1,164 opened on Jan 16, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Haskell (434 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (3,162 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the desired feature

This should be a fairly simple task because source maps already return offset and length of the expression in the source. We do line coverage with this function, which computes the line number https://github.com/ethereum/hevm/blob/6c876b24b61d2c8f8b9919cc668db9a03e6496c8/src/EVM/Dapp.hs#L179-L183. Instead, we can just use offset and length from SrcMap and color accordingly. For now, we should do it only for html and think how to do it with text and lcov formats (not sure if this is even supported).

Contributor guide

Research direction
Implement expression level coverage in the HTML report by using offset and length from SrcMap instead of computing line numbers. Refer to the existing line coverage function at src/EVM/Dapp.hs lines 179-183.
Tech stack
haskell
Domain
testingblockchain
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHaskell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75