Use undercover to check lisp test coverage #1574
Open
Conversation
This file contains hidden or 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
|
Note to myself: We ll have to cover properly Lisp code before merging this. |
galaunay
force-pushed
the
Lisp-coverage
branch
from
6a1285d to
c24d735
Compare
galaunay
force-pushed
the
Lisp-coverage
branch
from
c24d735 to
956e396
Compare
galaunay
force-pushed
the
master
branch
4 times, most recently
from
c4a2564 to
d974e00
Compare
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.
PR Summary
At the moment, coverall just check the test coverage of python files.
With this PR, undercover will be use to check for lisp files test coverage.