[WIP] Testing docs, JS lint, more tests?

[shawnbot]

• Add a test/data README.
• Clean up our JS so that it doesn't generate any errors when you run npm run lint-js.
• Remove some old/unused scripts.
• Switch to ESLint?
• Stub out some new tests for other data?

[gemfarmer]

Some other possible testy things

• add lint-js to circle.yml config
• add test-html to circle tests. First ensure that all tests pass!

[shawnbot]

I'm on the fence about adding lint-js (or lint-scss) to the CI config, unless we're planning on removing @houndci. The question is: Do we prefer the CI build to fail if we push code that doesn't meet the conventions, or do we want to continue be hounded in the pull request comments? My gut reaction is that having the builds fail outright seems a little extreme.

Also, we should try out the new ESLint setup referenced in 18F/frontend#98.

[shawnbot]

Also, there are lots of errors in lint-html. 😬 I'm not sure how many of them are valid, but we'll probably need to push that off into a separate issue.

[gemfarmer]

I would also prefer hound! Fine with pushing off lint-html til later.

[gemfarmer]

Thoughts on adding an accessibility check to Circle? This could also be pushed off to a new issue.