Slashdot Mirror
How Do You Test Your Web Pages?
Pieroxy asks: "As a web developer, both professionally and personally, I try to always make sure what I write works in every browser at my disposal. When the choice came for me to choose a platform for my PC, I went the Windows route, because I cannot afford not to test IE on all those websites/applications. But now I am facing a problem with all browsers that don't have a native Windows port, such as IE5/Mac, Safari/Konqueror. kde-cygwin helped very little because the version of Konqueror shipped doesn't display most JPEG, making any testing worthless. IE5 for Mac should die soon, but is still widely used as being the default browser for so long. How do you test your web pages? Have you noticed discrepancies on how a specific engine (Gecko, Opera, KHTML) renders content on different Platforms? Do I need a Mac and a Linux machine to make sure it is working on these platforms?"
>The whole point of testing in browsers is to ensure that things work properly.
The whole point of standards is that you don't have to. They will, all by themselves, if the browsers are standards-compliant.
If I validate xhtml 1.1, that's the end of my testing phase.
To address your question specifically:
>How do you ensure that the HTML, CSS, etc you have chosen works with popular browsers?
By using standard-compliant xhtml and css. In and of itself, this guarantees that this will work in particular browsers.
Note that I semantize, and don't go for special effects. (None. Go to my site, you'll see. It navigates and looks the same in Konq, Safari, Moz, Op, Lynx and Links.)
"Piter, too, is dead."