Implement an EUnit reporter #19
Merged
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
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.
This PR implements
doctest_eunit_report, an Eunit reporter/listener.The goal is to provide a better experience with
doctestin parallel with EUnit because EUnit is the basis of doc tests.doctest_eunit_reportdoctest_eunit_reportprovides a go-to definition for the exact location of the error and displays a portion of the code from where the error occurs, for example:eunit_progress| rebar3rebar3uses by default eunit_progress to print EUnit tests.doctest_eunit_reportvseunit_progressBelow is a simple comparison between both EUnit reporters.
eunit_progress
doctest_eunit_report