-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement asciidoctor-doctest testing #92
Comments
As mentioned by @mojavelinux, we should use rake for tests |
Rake for tests? o.O Rake is like Make… |
To run the tests, instead of make |
See #110 (comment) |
Faced a problem trying to get the tests to run, filed a bug to upstream project in order to get help: asciidoctor/asciidoctor-doctest#11 For anyone interested, work-in-progress branch is here: obilodeau/asciidoctor-reveal.js It is, again, due to my misunderstanding of the whole gem, bundler and ruby packaging ecosystem... |
Making some progress. Until further notice, refer to the pull request #116 to follow what is happening. |
With #116 in master, this has been implemented. |
We should implement asciidoctor-doctest. See asciidoctor-backends for an example implementation.
Idea / suggestion came from @jirutka during this discussion #63.
The text was updated successfully, but these errors were encountered: