Browser Testing Sequence

Here is an inter­est­ing post on what one web devel­oper does to test a site in all of the rel­e­vant browsers.

I think that it’s a good gen­eral descrip­tion of what browsers you should test and things to be look­ing at in each test.

For instance, some of the older browsers (like IE 5.5 and IE 5) aren’t worth your time to make the site look per­fect in them. It is how­ever prob­a­bly advis­able to at least make sure your site is still read­able and use­able in them (even if that means strip­ping out the JavaScript and CSS).

Gen­er­ally speak­ing, this is about the same process that I follow. I’m not nearly as vig­i­lant with all of the smaller browsers though:

When some­thing major (a full page tem­plate or a par­tic­u­larly tricky part of a design) is done I give it a quick check in the latest ver­sion of every browser that runs natively on Mac OS X. Cur­rently that means Camino, Flock, iCab, Netscape, Omni­Web, Opera, Sea­Mon­key, Shiira, WebKit Nightly, and any other newcomers.

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply