TestingWhiz vs BrowserStack: Which is a better fit?

Mike: Hi, my name is Mike. I'm a lead handshaker, and I give BrowserStack a five out of five. For more reviews like this, click below. Things that we were using before BrowserStack, was just testing on local devices, installing a bunch of browsers on all the different computers, talking to that one guy at the office that happened to have a Mac and just do the testing locally. The reason we chose BrowserStack is quite simply, it's the only solution that I'm aware of that allows you to test on hundreds of browsers and operating systems on actual hardware without emulation. For just the basic testing and live testing, it's super easy to get started. You can get onboarded within a couple of minutes, and your team can start testing different web interfaces, local environments, and putting in bug reports to get all that stuff fixed. At my last agency, we actually used BrowserStack Automate and actually did some selenium testing to make the process even quicker and that only took our dev team about two weeks to fully integrate into. But if you are 95% of the work that we do with BrowserStack, it's just, you want to test on a bunch of browsers or a customer said they had an issue on Firefox, and you just want to be able to reproduce it, you can get up and running with just a couple of clicks. If you're thinking about using BrowserStack, first of all, do yourself a favor and do testing. Don't think just because it works on Chrome on Windows, it's going to work in Chrome on Mac, and don't forget about the lesser known browsers. Also, if your project is open source, and you can point to a public open source repository like a GitHub or Bitbucket, they have very generous, complimentary open source licenses available for your project, so definitely check that out.