Headhunter

Headhunter is an HTML and CSS validation tool that injects itself into your Rails feature tests and automagically checks all your generated HTML and CSS for validity.

In addition, it also looks out for unused (and therefore superfluous) CSS selectors.

This is all done locally, so no external service is used.

Add Headhunter to your Gemfile:

group :test do
  gem 'headhunter'
end

Just set the environment variable HEADHUNTER to true when running your tests, e.g.:

$ rake HEADHUNTER=true
$ HEADHUNTER=true rspec
$ HEADHUNTER=true cucumber

Headhunter doesn't keep your tests from passing if invalid HTML or unused CSS is found. Instead it displays a short statistic after the tests are run.

Headhunter registers itself as middleware in the Rack stack and triggers validation for every HTML response. Headhunter also iterates over every .css file and triggers its validation. In addition, it checks which CSS selectors are really used in the HTML pages to see whether there exist any unused CSS definitions.

For being able to validate CSS, rake assets:precompile is triggered at the beginning of running tests. This may slow down starting your tests a bit. Notice: all precompiled assets will be removed after the tests have finished!

Please keep in mind that this is a pretty early release. I didn't have the possibility to test it extensively yet, so there surely are a lot of things left to do. You are highly welcome to file issues, add feature requests and open pull requests.

A local copy of Tidy HTML is used. It's the [experimental HTML5 version]((http://techblog.willshouse.com/2013/10/21/homebrew-tidy-html5/), compiled on OSX using homebrew. If you're on Linux and it doesn't work for you, please replace the executable in lib/tidy.

You need a Java Runtime Environment to run CSS validation. This should normally already be available on OSX and Linux machines, too. A local copy (css-validator.jar) of the W3 CSS Validation Service is used.

• Test on Linux! Add switch to use linux-compiled version of tidy if needed.
• It would be nice to use Rails' own assets compilation that's executed when the first JavaScript test is run. Anyone has an idea on how to do this?
• HTML and CSS sources should not be uglified, to allow more concise error messages
• Would be really useful to have the concrete URL of every validated HTML page. But can't find a way to extract it from Rack response.
• Didn't try this with AJAX requests yet. Would be great if such responses would be validated, too!
• More configuration options needed! CSS1, CSS2, CSS2.1, CSS3! XHTML, HTML5, etc.
• Better output needed! With context lines, etc.
  • HTML output: info about GET/POST/PUT/DELETE!
• Look out for multiple used IDs on the same page and raise error (tidy doesn't seem to do this?!)!
• Look out for invalid tags and raise error (tidy doesn't seem to do this?!)!
• Cache HTML validations: use MD5 to prevent validating the same source again and again! (Maybe even keep the cache between running specs!)
• Add option to CssHunter that ignores "bare" rules like applet, blockquote, etc. (which usually stem from libraries like Compass reset or Normalize)
• Add option to specify known invalid/unused tags, attributes and selectors (e.g. aria-* or ng-*).
• Add option to ignore vendor prefixed attributes.
• Add option to make Headhunter automatically remove unused CSS selectors from compiled file

Headhunter is heavily inspired by Aanand Prasad's Deadweight gem, Eric Beland's HTML Validation gem and Unboxed Consulting's be_valid_asset gem. Thank you for your pioneering work!

USE THIS GEM AT YOUR OWN RISK!

All provided functionality is provided "as is".