Reliable Cross Browser Sites

[Wyndru]

There are a lot out there, I don't want to put my site url on a lot of them, anyone have suggestions on a cross browser test site? I need to verify some non critical php code.

 

[Cogman]

I've always went with manual testing. I mean, really, the only browser out there that breaks things is IE5, 6, and 7. Everything else pretty much does the same job. After that, you could test with firefox and chrome which covers 99% of your users (as firefox and chrome use the same web rendering tech as a whole ton of other browsers) followed by Opera.

IE8, 9, and 10 have gotten there acts together and are now pretty standards compliant.

 

[Ken g6]

@Cogman: I recently found that IE8 doesn't support an XPath locator for elements, like every other browser I know of does.

So, basically, still test on IE. :\

 

[Cogman]

@Cogman: I recently found that IE8 doesn't support an XPath locator for elements, like every other browser I know of does.

So, basically, still test on IE. :\

yeah, but it is MUCH better than IE7 was as far as compliance goes. If you get something to work on IE7 and firefox, you should have like 99% of your users covered.

 

[Ka0t1x]

Manual testing is probably the easiest way. When I'm doing any HTML/CSS I've always tested it using a separate machine. Main machine is running OSX and I will have a VM of 7 and XP running on the MacBook Pro.. I can do all of my browser testing from one machine. (Configuring Synergy will complete this cycle)

Snapshot a VM at first install/setup for Windows and always revert back to the snapshot before testing = clean slates.

 

[Cogman]

One thing, while it is pretty much impossible to test for layout stuff without manual testing, you can do a lot of functional testing automatically.

http://seleniumhq.org/

Here is what we use at work to test the functionality of our stuff.

 

[Wyndru]

Yeah for some reason the php code wouldn't work in IE8, but in Firefox it worked fine.

I ended up fixing it by using some of the validation tools from this site:
http://www.w3.org/QA/Tools/

The issue was that IE8 wanted a specific doctype declaration that Firefox didn't care about missing.