Dreamweaver will have a browser testing screenshots functionality / service attached. Like browsershots service.
I personally don't see the point, testing dosn't mean LOOKING does it, its a browser looking service, not testing.
With most browsers these days pretty good at CSS and IE6's CSS issues easily predictable, little rendering differences are arguably less important than the AJAX fancy stuff that could get broken. If you can't test full functionalities and navigate around the site in the real browser, you just can't tell if its working.
For example, I visited a company's portfolio site the other day in safari 3, I'm guessing the big white box on homepage was meant to be a fancy slideshow, but all i saw was a big white box. DOH!!! epic fail. White box was only thing on the page!
More and more sites, especially minimal portfolio style sites are reliant on fancy Jquery type galleries and effects, or have fancy menus or popups for essential content. If the gallery script fails or is unbearably slow on a certain browser, its just not acceptable to not know about it. I can handle not knowing exactly what typeface konquerer has rendered my body copy in, but I cant handle that if some random nerd happens to find the site that major parts of content are completely inaccessible. Then again said nerd will hopefully understand and empathise...
Posts
