Closed jwflory closed 4 years ago
This should make the CI tests pretty snappy. For what it's worth, I moved my personal site over to a Jekyll static site and implemented the same method of CI in jwflory/jwflory.github.io@8c383a414bc2a786eb7dac1ba779d5258742d4d0. Works well and when the tests are cached, the build took less than a minute. :sparkles:
Thanks @kennedy! Merging. :shipit: :clapper:
This refactors the way the test suite is ran according to the html-proofer documentation:
https://github.com/gjtorikian/html-proofer/wiki/Using-HTMLProofer-From-Ruby-and-Travis
I like this approach better because it uses the existing "test" imports in the
Gemfile
and allhtml-proofer
config options are set in theRakefile
instead of a really long command string in the.travis.yml
.Additionally, this also adds a check for valid HTML to
html-proofer
since it is disabled by default. Seems like a useful thing to have.:gem: Add rake to Gemfile, update Gemfile.lock