Can you give me some guidance about how to optimize our browser compatibility testing?
There are a couple of strategies that I’ve used to optimize testing time in what I think of as “cross browser” testing.
1) Work closely with the developers, and listen to their ideas and guidance.
2) Learn the vulnerabilities of the website you’re testing.
Although guidance from developers is great, there’s no reason I can’t do some investigation on my own. I use View Source on a Web page to become familiar with the inner workings of pages and functional areas. Over time, experience with the application leaves me knowing where to look, but when a new page or new feature is added or I’m working with a site for the first time, this is one way to do some investigating. Another is looking over defects to find areas of the application that are vulnerable. Past knowledge is helpful.
3) Use the “other” browser.
I’ve written on the topic a number of times, so it’s probably no surprise to hear me mention languages. I work with Right to Left Languages frequently enough that I often look to different browsers to check scrollbars, displays and diacritical marks to think about not just other browsers but other languages. In the case of cross browser testing it’s the handling of Right to Left languages that I’m most on the prowl for.
Dig Deeper on Topics Archive
Related Q&A from Karen N. Johnson
User acceptance testing and system integration testing differ in one key way: the person who does the testing. Learn when to apply UAT vs. SIT. Continue Reading
There are so many resources out there about the ever-changing world of Web design and mobile testing, but to choose the most salient and insightful ... Continue Reading
Initiating test automation on your project team may seem challenging, or even overwhelming. Fortunately, expert Karen Johnson has been through this ... Continue Reading