"@BrowserStack is AMAZING. So glad we chose them for our browser testing. Now they even have mobile testing!"

"While one side is revenue, the other is reputation. If there are issues in processing payments, people lose trust, which is even worse than losing money."

"The other added advantage of BrowserStack is access to Internet Explorer browsers, which we can’t do on a Mac machine. Some of our applications still need Internet Explorer support, so at least via BrowserStack, we can test on Internet Explorer."

"BrowserStack enables the best browser support. Without it, reproducing and resolving bugs would be much harder. New bugs could be introduced during development without us noticing. We use it everyday!"

"Now instead of having to manually scout for visual changes across all of our pages and components in every pull request, we instantly see everything that’s changed in Percy’s UI."

"I love @browserstack! Great product and awesome support. Thanks for helping me today and have a great weekend"

"The move to BrowserStack has been a force multiplier across all teams. It is a core and critical part of our build and release infrastructure, and every engineer ultimately depends on BrowserStack in one way or the other."

"Some things can’t be easily tested with unit tests and integration tests, and we didn’t want to maintain a visual regression testing solution ourselves. Percy has given us more confidence when making sweeping changes across UI components and helps us avoid those changes when they are not meant to happen."

"Our ultimate goal is continuous delivery. BrowserStack is one major part in developing that capability."

"Before BrowserStack, it took eight test engineers a whole day to test. Now it takes an hour. We can release daily if we wanted to."

"Just played around with BrowserStack Quite cool, instant access to a browser in a VM with dev tools."

"@dietrich the best is @travisci + @browserstack : ) using Selenium or PhantomJS/SlimerJS."

"Enjoying @browserstack to quickly test things in IE8 to make sure they break accordingly."

“We cannot afford having bugs in production. That’s why we avoid rollbacks. We try to identify the bug before we release.”

"We use BrowserStack for manual testing and in Travis-CI for running our tests via the Karma test runner in a wide variety of browsers. We use it before cutting every release of Video.js and it’s prevented multiple bugs."