Ask HN: How do you test for browser compatibility?

3 points by _ix ↗ HN
I've taken over for a failing project at work, supporting the largest contract my company has ever executed. We're understaffed in my department, and by taking over, I mean I'm solely responsible for everything. Until now, it's been a jumble of band-aids and temporary fixes. After a couple of weeks of database tuning and other architectural changes, I'm starting to focus on the browser. Unfortunately, the sales people here wrote nothing about browser support in the contract, so we're on the hook for supporting anything the client uses. IE7 tends to be particularly problematic with subsequent builds. Any radical changes I make seems to break a lot of functionality for the client after I've pushed the changes to production, but the real problem is that I can't see it in my (manual) testing procedures before the client does -- I'm just using IE11 with the developer tools mimicking IE7 functionality. Everything's beautiful in Chrome, Firefox, and IE9+ isn't bad at all...

tl;dr: How do I really see if things are breaking across browsers and browser versions? How can I automate my browser testing procedures?

5 comments

[ 3.8 ms ] story [ 17.6 ms ] thread
There was an HN story about http://nightwatchjs.org/ here recently. It's a nice wrapper around Selenium WebDriver that enables testing across browsers automatically from a test runner. Not used it yet but it does look good.

There are many other wrappers around WebDriver too.

Very cool. I'll take a look into this now. Thanks for the suggestion.