This looks like a tool you'd use for debugging / manual testing. htmltest
can be used in that manner but it's best suited to be part of a deployment
pipeline. For example I have a site that builds on push and if successful
deploys to a static host. Very useful foe keeping editors from breaking the
site!
This site has over 2000+ pages, having a tool to validate the output is
akin to test suites in a software project, ensuring anything pushed to prod
is free (at least for what we check for) from faults.
On Tuesday, 15 November 2016 04:55:42 UTC, Egor Smolyakov wrote:
>
> Recommend to see this project -- http://www.validity.org.uk/
>
> понедельник, 14 ноября 2016 г., 22:51:25 UTC+2 пользователь Will Pimblett
> написал:
>>
>> Hi,
>>
>> This is a bit of a general post, not really a precise question. I've
>> built a go application to test the validity of generated HTML markup (the
>> sort you'd make with a static site generator, like Hugo or Jekyll) based
>> loosely on an existing ruby gem html-proofer. It runs files through a
>> series of checks to ensure all links, images, and scripts references work,
>> alt tags are filled in, Rather useful in a static site CD pipeline.
>> I've toyed around with Go previously but never built anything with it, this
>> is my first 'real' project.
>>
>> I'm posting here to advertise it to those who may find it useful, and if
>> anyone is willing: to garner feedback over the codebase. I've tried to pick
>> up as many Go idioms as possible but will surely have made many mistakes.
>>
>> https://github.com/wjdp/htmltest
>>
>> Cheers,
>> Will
>>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
