Assuming your web AUT(application under test) has lot of features which will result in huge number of testcases. Let's say AUT has hundreds of testcases as it has been the case for me, most of time. Basic requirement for test team is to make sure all features works fine on every web browser we support. Best way to achieve this is to run every testcase on every browser which will be an exhaustive way. I really don't like this way and I feel there should be a way to optimize this. Validating your web application for all web browser is callled cross-browser compatibility thats what i am going to focus on .
From my experience what I have discovered is that there are two areas where behavior of your application changes from browser to browser. If I concentrate on those two areas then I can optimize on testing for browser compatibility.
Those areas are
- CSS is guidelines which tells browser how to display your page. These guidelines are stored in a file( with .css extension) with web pages.There are standard for these guideline but different browser interpret these files differently, which causes your web pages to display incorrectly. Most common issue you will find due to CSS are,
- label size not proper.
- Text font vary across browser.
- pop-up menu does not render properly. In general you can say all UI rendering issues.
- navigate through all pages/dialog box and popup menus on your web application.If there is any UI problem due to CSS you will easily observe it .
According to me, if you attack these two areas you can optimize on browser compatibility and avoid running every testcase on every browser.