Support for REPL-simulated test cases #2
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
andreypopp
force-pushed
the
master
branch
2 times, most recently
from
c1b589b
to
83acf8f
Compare
|
Thanks for the PR! This seems useful to me. Different |
andreypopp
changed the title
|
Alright, I've cleaned it up and added more tests. |
The implementation is based on the code from Documenter.jl.
Allows to define test cases with REPL-simulated syntax:
julia> 1
1
This is useful as allows to define new test cases by simply copy pasting
real REPL sessions.
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.
The implementation is based on the code from Documenter.jl.
Allows to define test cases with REPL-simulated syntax:
This is useful as allows to define new test cases by simply copy pasting real REPL sessions.
If you think this is useful I can improve the test suite (now the test execution isn't tested and it should be as code path is altered to use same output display as in REPL). Otherwise I'm fine with vendoring NarrativeTest.jl in my code directly if you think the package should stay as-is.