Setup coverage with undercover/coveralls #37
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
AdrieanKhisbe
force-pushed
the
setup-coverage
branch
from
3efc896 to
a1f691a
Compare
Contributor
Author
|
@rejeep Just rebase the branch, |
| (require 'ert (f-expand "ert" espuds-test/vendor-path))) | ||
|
|
||
| (require 'undercover) | ||
| (undercover "espuds.el") |
Contributor
There was a problem hiding this comment.
Do you need to set a report file here like you do for ecukes?
Contributor
Author
There was a problem hiding this comment.
in this case nope, the default report file will suits.
We need to specify one when we need to merge the result between ecukes and ert as we do in ecukes repo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.