3 ms·

> Front-end developers have to test against Chrome, Firefox, and Safari, at a minimum. Do many companies actually do this though? I've only ever been with com

> Front-end developers have to test against Chrome, Firefox, and Safari, at a minimum. Do many companies actually do this though? I've only ever been with companies that test against Chrome. The one time at FF bug was found, that company told that client to switch to Chrome. I know there was a kerfuffle about Airbnb and Groupon only doing Chrome as well. https://www.reddit.com/r/AirBnB/comments/dv7v6n/customer_support_our_platform_is_designed_to_work/ https://www.reddit.com/r/AirBnB/comments/dv7v6n/customer_sup... https://thenextweb.com/dd/2017/11/28/please-build-websites-web-not-just-google-chrome/ https://thenextweb.com/dd/2017/11/28/please-build-websites-w... Maybe in theory all platforms are considered, but in practice many companies just do one and the others mostly just work.

joshuacc 6y ago
Yes, absolutely. Every company that I've ever worked at had a list of officially supported browsers that included Chrome, FireFox, Safari and Edge/IE. QA engineers would make sure to rotate through various browsers while testing, and for crucial features would run through every scenario in every supported browser's oldest and newest supported versions.
- hinkley 6y ago
  Pretty much the only reason to use Saucelabs is browser compatibility testing. We don't run everything through it, but we run karma to make sure the code runs and the right events fire. It is still possible to write code that runs everywhere but IE.
swagonomixxx 6y ago
In a previous company we had to do FF and Chrome. Not IE though, which was a big time saver. QA ran all their test cases on the latest stable of both FF and Chrome, and features would not be deployed to prod if they didn't work on both browsers.
calibas 6y ago
Most companies today use frameworks that have good cross-compatibility so it tends to just work. In my opinion though, a responsible web developer is going to test on multiple browsers at the very least.
tambourine_man 6y ago
Safari is huge. Doing Chrome only is suicide. Thankfully, cross browser compatibility is much easier these days, specially if you don’t use flex or grid.

joshuacc 6y ago

Yes, absolutely. Every company that I've ever worked at had a list of officially supported browsers that included Chrome, FireFox, Safari and Edge/IE. QA engineers would make sure to rotate through various browsers while testing, and for crucial features would run through every scenario in every supported browser's oldest and newest supported versions.

hinkley 6y ago
Pretty much the only reason to use Saucelabs is browser compatibility testing. We don't run everything through it, but we run karma to make sure the code runs and the right events fire. It is still possible to write code that runs everywhere but IE.

swagonomixxx 6y ago

In a previous company we had to do FF and Chrome. Not IE though, which was a big time saver. QA ran all their test cases on the latest stable of both FF and Chrome, and features would not be deployed to prod if they didn't work on both browsers.

calibas 6y ago

Most companies today use frameworks that have good cross-compatibility so it tends to just work. In my opinion though, a responsible web developer is going to test on multiple browsers at the very least.

tambourine_man 6y ago

Safari is huge. Doing Chrome only is suicide. Thankfully, cross browser compatibility is much easier these days, specially if you don’t use flex or grid.