By the way, I've noticed a small bug, the website seems to try to load http://localhost:35729/livereload.js so you should check your sources to modify this to the production URL.
Really like this idea. Haven't been able to test it out yet due to HN overload. Will check it out again later.
Also, on the pricing tables. Headers and some text acting up with the responsive design for small screens.
> Pending
> Oops, an error occured. Please contact us for support or try again.
;)
If you get "Oops: Request to start crawl failed" and click "Try It Out" again and again you get a lot of duplicate messages.
Are there any types of checks you plan to do in the future that you're not doing now?
We want to do lots and lots of checks that we don't currently do, e.g. linting the JS, correct MIME type checking, screenreader support, SEO, HTML/CSS validation, i8ln, intelligent form submitting, different browser agent support, responsive design, external font rendering
The hard part so far has been getting the crawler right, as some of you can probably see it's still a bit buggy.
Relative location headers are in HTTP 1.1 so we should respect them: http://en.wikipedia.org/wiki/HTTP_location#Relative_URL_exam...
Also the business plan offers crawling for 50 websites. Is this plan aimed at digital agencies? If it is then that's good but if not then that number is probably too high and more links per crawl might be better?
Thanks for the feedback on the pricing. You may be right, we probably need another plan that handles more links and less sites.
[1] nightwatchjs.org
We've been using Pay4Bugs though (http://www.pay4bugs.com), it's a crowdsourced solution. You should get together with them!
Nothing beats having a ton of bug finders with different browser versions or phones... Some things just can't be automated.
Bughunt aims to find bugs a real user would run into.
It does this by using an actual web browser to crawl (not just HTTP requests). This means it supports Single Page Apps, JavaScript and anything else (including external scripts & images) that the page requires to render correctly.
Bughunt can replace a large chunk of point and click QA regression testing, without ever having to write automated scripts.
As already suggested, would be nice not needing to specify scheme.
Woops.