Browser Specific TestFixtures Sharing Tests is from the same person as above and shows how to abstract different browsers from the script by moving the browser choice up to the suite level. Not sure how this would scale though…

I would really like to see less ‘howto’ blog posts that repeat the same basic information and more experience reports like deja vu: code, culture, and QA. Oh, and it serves as a nice reminder that automation is more than just regression; its about producing information that starts conversations

JSErrorCollector solves for Firefox something I think is missing from Se — which is the collection of JS error messages from the browser. (And it is missing from it for a reason; browsers don’t always expose it. Maybe we can get that into the W3C spec…)