We take testing seriously, and have years of experience with oddly behaving rendering engines and spending night shifts debugging weird Internet Explorer 7 bugs. To make sure the final result works on as many platforms and devices as possible, we usually start testing early on. Due to the vast amount of devices that are in the market (like 15000+ Android Devices) and the abundant versions and types of browsers they carry, we just couldn’t go through them all so we do something clever for our testing workflow.
As we do have access to plenty of real devices that cover the most common screen resolutions on desktop, tablet and mobile as well as all popular operating systems (Windows, MacOS, Android and iOS), we use those for aggressive testing and go through all the latest versions of Chromium Browsers, Safari and everything in-between.
As for the notoriously difficult Internet Explorer, we can cover version 10 upwards and usually use Microsoft’s very own virtual machines to thoroughly test the user experience in their browsers. And we also use tools like BrowserStack to back up our results, which gives us access to a huge number of testing devices and browsers (including older versions of self-updating browsers like Chrome or Firefox).
We approach browser and device testing with accessibility and usability in mind, to provide the best possible experience for the user groups we’re targeting. While a project might not always have the budget to test as thoroughly as we might like, we’re aware of the risks that come with inadequate testing. So we try to do our very best to continuously do this from the project’s early stage to it’s finish so that we don’t get surprises from anywhere!
