If you generate HTML files, html-proofer might be the tool for you. If you can't be bothered with a Ruby environment or fancy something a bit faster, htmltest may be a better option.

🔍 htmltest runs your HTML output through a series of checks to ensure all your links, images, scripts references work, your alt tags are filled in, et cetera.

🏇 Faster? Yep, quite a bit actually. On a site with over 2000 files htmlproofer took over three minutes, htmltest took 8.6 seconds. Both tools had full valid caches.

😕 Why make another tool: A mix of frustration with using htmlproofer/Ruby on large sites and needing a good project to get to grips with Go.

This godownloader script will query GitHub for the latest release and download the correct binary for your platform into the directory set with the -b flag.

curl https://htmltest.wjdp.uk | sudo bash -s -- -b /usr/local/bin

You'll be prompted for your password. After simply do htmltest to run.

curl https://htmltest.wjdp.uk | bash

By default this will install htmltest into ./bin of your current directory, to run do bin/htmltest. Rather suitable for CI environments.

Run curl https://htmltest.wjdp.uk | bash -s -- -h for help text.

We're available in some package repositories such as Homebrew and repos for certain distros. Do note the version available may not be the latest.

⬇️ Download the latest binary release and put it somewhere on your PATH.

docker run -v $(pwd):/test --rm wjdp/htmltest Mount your directory with html files into the container and test them.

If you need more arguments to the test run it like this: docker run -v $(pwd):/test --rm wjdp/htmltest -l 3 -s

We store temporary files in tmp/.htmltest by default. This contains a log of output and a cache of external links, speeding up subsequent runs. You probably want to ignore it in version control, and perhaps cache it in your CI system.

htmltest - Test generated HTML for problems
           https://github.com/wjdp/htmltest

Usage:
  htmltest [options] [<path>]
  htmltest -v --version
  htmltest -h --help

Options:
  <path>                       Path to directory or file to test, if omitted we
                               attempt to read from .htmltest.yml.
  -c FILE, --conf FILE         Custom path to config file.
  -h, --help                   Show this text.
  -l LEVEL, --log-level LEVEL  Logging level, 0-3: debug, info, warning, error.
  -s, --skip-external          Skip external link checks, may shorten execution
                               time considerably.
  -v, --version                Show version and build time.

Many options of the following tests can customised. Items marked 🔜 are not checked yet, but will be soon.

• a link img script: Whether internal links work / are valid.
• a: Whether internal hashes work.
• a link img script: Whether external links work.
• a: 🔜 Whether external hashes work.
• a link: Whether external links use HTTPS.
• img: Whether your images have valid alt attributes.
• link: Whether pages have a valid favicon.
• meta: Whether refresh tags are valid and the url works.
• meta: 🔜 Whether images and URLs in the OpenGraph metadata are valid.
• meta title: 🔜 Whether you've got the recommended tags in your head.
• DOCTYPE: Whether a doctype is correctly specified.

I'd like to test the following but won't be for a while.

• Whether your HTML markup is valid. htmlproofer has the ruby library Nokogiri, I've not found one for Go yet.

Add the data-proofer-ignore attribute to any tag or to the class of a tag to ignore it from every check. The name of this attribute can be customised.

<a href="http://notareallink" data-proofer-ignore>Not checked.</a>

Checking external URLs can slow tests down and potentially annoy the URL's host. htmltest caches the status code of checked external URLs and stores this cache between runs. We write the cache to tmp/.htmltest/refcache.json and expire items after two weeks by default.

By default, output in the TTY uses colours to indicate warnings, errors, and success. To turn off colourization, set an environment variable named NO_COLOR. If it is present, no colour will be used. The value is ignored. (See no-color.org.)

If you've got a lot of errors, reading them off a TTY may be difficult. We write errors to tmp/.htmltest/htmltest.log by default. The log level is set in the config file.

htmltest uses a YAML configuration file. Put .htmltest.yml in the same directory that you're running the tool from and you can just say htmltest to run your tests. You'll probably also want to cache the tmp/.htmltest directory.

DirectoryPath: "_site"
EnforceHTTPS: true
IgnoreURLs:
- "example.com"
- "^/misc/js/script.js$"
IgnoreDirs:
- "lib"
CacheExpires: "6h"

Submit an issue.