Skip to content
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

Add coverage report #167

Open
karmacoma-eth opened this issue Aug 11, 2023 · 0 comments
Open

Add coverage report #167

karmacoma-eth opened this issue Aug 11, 2023 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@karmacoma-eth
Copy link
Collaborator

Halmos systematically explores as many paths as possible, we should add some option to produce coverage reports.

Some unordered thoughts:

  • we operate at the bytecode level, should we print a report about bytecode-level coverage or try to report something about source level information? (lines, functions, branches, etc)
  • what about bytecode metadata, constructor arguments and other non-executable stuff?
  • how hard would it be to produce an lcov report for integration in CI? for instance the farcaster repo has a great coverage CI integration 👌
  • at a minimum, a summary like this would be neat:
 Summary coverage rate:
  lines......: 98.8% (238 of 241 lines)
  functions..: 98.5% (64 of 65 functions)
  branches...: 98.5% (128 of 130 branches)

Related:
http://ccadar.blogspot.com/2020/07/measuring-coverage-achieved-by-symbolic.html
https://blog.regehr.org/archives/386

@karmacoma-eth karmacoma-eth added the enhancement New feature or request label Aug 11, 2023
@daejunpark daejunpark added the help wanted Extra attention is needed label Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants