Hacker News new | ask | show | jobs
by joealba 3869 days ago
Since this is a Jekyll site, I'm not sure what we could wrap tests around. The beauty of the static site generator is that it just always works -- at least as far as the html content is concerned.

Is there a specific javascript feature or interactive feature that you'd like help with testing?
1 comments
llimllib 3869 days ago
It does work great! We've gotten this far without them. But it makes me nervous.

I'd like to have a few smoke tests to guard against things like:

* accidental deletion of pages

* accidental removal of header/footer/important elements

* proper 508 compliance

* valid HTML/JS/CSS (and probably lint all those things too)

Also the facility locator is a fair-sized hunk of JS I wrote that needs tests.

edit: also, in the future there will surely be more dynamic parts to the site, so getting a framework in place for tests will both save work and raise the expectation of quality

link
zaroth 3869 days ago
It's more like you want a linter with custom rules for how you think a page should look. Actually, it's impressive to create the entire site with only content and simple layout. It's interesting there isn't a better way to manage and edit all that content...

508 Compliance is another interesting point. Open source scanner to assess if a page complies? It's another linter, it has to look at the html. I don't know much about 508 but I'm going to say from a quick look at your <html> that it's as clean as you could possibly hope for, and I would expect that latest screen reading tools would be able to navigate it. If that's not the case it says more about the particular reading tool than the website.

The facility locator! That was interesting, the default state is everything selected, please flip it to everything deselected. I haven't tried it out more because it overloaded ;-)

Benefits comparison tool also looks like it has a pretty big data set behind it, that was probably cool to develop.

link