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

Running the tests #377

Closed
agriffis opened this Issue Oct 15, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@agriffis

agriffis commented Oct 15, 2016

To get the tests running, I used this sequence. I didn't see anything like this in the README or docs so I'd like to know if this is the best formula or if I should be doing something else. If this looks good, I can provide a pull request to add it to the README

$ rake gemspec  # makes kramdown.gemspec
$ cat > Gemfile <<EOF
source 'https://rubygems.org'
gemspec
EOF
$ bundle  # installs the dev deps
$ rake  # runs the tests
@agriffis

This comment has been minimized.

agriffis commented Oct 16, 2016

Additionally required for the test suite to run through cleanly

$ sudo dnf install nodejs npm
$ npm install mathjax-node
$ PATH=$PATH:$PWD/node_modules/.bin

and to include the latex tests (though these won't make the suite fail if missing)

$ sudo dnf group install 'Authoring and Publishing'   # Fedora
$ sudo apt-get install texlive-full  # Debian/Ubuntu
@agriffis

This comment has been minimized.

agriffis commented Oct 16, 2016

Hmm, this would have been easier if I'd noticed .travis.yml effectively laying out the requirements.

@gettalong gettalong self-assigned this Oct 16, 2016

@gettalong

This comment has been minimized.

Owner

gettalong commented Oct 16, 2016

Yes, the travis configuration file nicely shows what is needed. I will probably make a notice about this in the readme file.

@gettalong

This comment has been minimized.

Owner

gettalong commented Nov 9, 2016

I have added some info to the README.md file - thanks for making me aware of this!

@gettalong gettalong closed this Nov 9, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment