-
Notifications
You must be signed in to change notification settings - Fork 4
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
Generate .lcov
report
#11
Comments
This was
linked to
pull requests
Aug 26, 2024
Merged
Merged
ksew1
added a commit
that referenced
this issue
Aug 28, 2024
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The overview
We should generate
.lcov
reports using: #9 and #10The reports shall include:
We should omit branch coverage at this stage.
Lines in coverage are marked:
Reports shall be generated based on cairo vm trace pc's, we should consider a single contract execution for now (only the root of the profiler trace).
Lines states
hitable - covered - green 🟢
Happens when there is a corresponding casm instruction in mappings
and
in cairo vm trace there is a pc pointing to this instruction
hitable - missing - red 🔴
Happens when there is a corresponding casm instruction in mappings
and
in cairo vm trace there is no pc pointing to this instruction
not hittable - no color ⚪
Happens when there is no corresponding casm instruction in mappings, this happens if some code is removed by the compiler, inlined etc.
The text was updated successfully, but these errors were encountered: