First off, I'm not great at testing; I'll come right out and say that. But I've had a few issues lately and am curious how I'd automate testing to safeguard features. Here's the scenario:
On the beta signup form for DayTrip, I wanted to use the new fetch()
API as a replacement for jQuery and $.ajax
. Using this across all browsers requires two polyfills, a Fetch Polyfill and a Promises Polyfill. The form has has broken twice now which is not ideal for a new product.
- First time was just ignorance, didn't realize I needed a Promise polyfill for some modern browsers, even tho that's documented on the Fetch polyfill.
- Second time was a botched Asset Pipeline. The polyfills weren't included in my
home.js
, maybe due switching torails_12factor
, still not sure.
| | Edge | Mobile Safari | Chrome |