So you’re convinced. You decide to test your application on a few extra browsers. Chrome, Internet Explorer, Safari, and Firefox. To your dismay, you find that your website doesn’t display properly in Internet Explorer. Some tables are not aligned and a few of your menus don’t work in Chrome. You realize that you have to redesign your entire workflow and correct significant bugs right from the ground up to ensure that you have cross browser compatibility. You are in danger of missing your project deadlines, overshooting your budget, and your code is now messy and susceptible to further errors as well. If only you had incorporated cross browser testing right from the start, you wouldn’t face any of these problems.
It may seem as if there are only a handful of major browsers on the market. And indeed, if you want to only cater to “most” of the population, you can get away with testing on 3 to 4 web browsers alone. However, keep in mind that there are certain geographical locations where a particular browser is used almost exclusively even though its share in the world market may be low. If you want to reach people in these areas, you have to ensure that you test your web application thoroughly with even those browsers that have a miniscule market share. We are after all talking about the World Wide Web where even 2% can translate into millions of users.
And don’t forget that you also have to test with many versions. If you look at Internet Explorer, a significant number of people are stuck on older platforms. In some cases this might be linked to the operating system which doesn’t support the upgraded browser. As you can see, cross browser testing of your application is of critical importance from the ground up. Not just as a mere afterthought. But don’t worry! There are several tools that can help you with this and which you can use to automate the process as much as possible.
Photo by Jean-Etlenne Minh-Duy