Add code coverage reporting #74
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I tried compiling a simple hello world OCaml program via |
|
Following some of the tips described in SimonKagstrom/kcov#242 (comment) what seems to be happening is that dune sandboxing is causing the paths to not be found by kcov, which is why things work with manual compilation with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2.
Generated code coverage: https://mt-caret.github.io/polars-ocaml-kcov/kcov-merged/index.html
Taking a quick look at the coverage information, it's already quite useful. For example, I didn't realize that we don't really execute the
ThenandChainedThenclauses inrust_expr_when_then; probably worth adding a doctest.