Every web designer who works extensively with HTML and CSS knows that debugging a website in IE (no matter what version) is the equivalent to slowly plucking every hair from your head. There have been endless amounts of articles written on it from the amateur to the influenial – explaining everything from how to hack it (ahhhh!) to how to learn to love the bomb.
To date, perhaps the most frustrating part of cross-browser testing in IE has been the ability to run your websites in multiple versions of the same browser. As the web design world knows, Microsoft has put a cap on how my versions of IE can be running on a windows machine and that cap would be one. Now, there have been many ways around this – all of which have their ups and downs: installing multiple virtual environments that support different IE versions (ick); using a web app that takes screenshots of your site in IE; or using applications that are capable of installing multiple versions of IE thus letting you test to your heart’s content.
I’ve tried all the ways above, the last having up till now been my choice of posion. However, recently (in my terms, not in terms of when the program was released) a new level of multiple IE testing has surfaced for the good of all designer-kind: <a href=”http://www.my-debugbar.com/wiki/IETester/HomePage” rel=”nofollow”>IE Tester</a>.
This is the holy grail of IE testing that we’ve all been waiting for – yes, it’s alpha; no, it doesn’t have debugging toolbars; but all those aside, HALLELUJAH!
Created by the same genius who made the IE debug bar (which has served me in countless ways over the years) this nifty little program installs on your windows system (XP and Vista) and lets you cleanly view the world through IE eyes. It’s admitted that it’s alpha, so bugs are more than likely probable; however, this little baby packs a major punch now and can only grow finer with time. The interface is sleak and lets you use tabs to keep track of your opened versions of IE. In addition, it supports a wide assortment of versions, including the very beta IE 8. But the creme de la creme for me – it doesn’t denote to the highest IE browser setting when you use conditional comments, so IE 6 is IE 6 and IE 7 is IE 7 and the world just became a slightly better place for me to test in.
I’m hoping this cures my IE testing woes for years to come, as I’ve already seen it work magic in my testing days now, and I’m incredibly excited to see where this progresses in the future.