Thursday, March 8th, 2007
He discusses the issue of each browser introducing more bugs (a fix to some is a bug to others!) and shows how Mozilla is trying to help out:
Doing this will provide, at least two, huge benefits:
- Library developers will be able to know about unavoidable regressions and adjust their code before the release even occurs.
- Mozilla developers will be able to have a massively-expanded test suite that will help to catch any unintended bugs. In addition to making sure that less, general, bugs will be introduced into the system, library authors and users will be content knowing that their code is already working in the next version of Firefox, without having to do any extra work.
What progress has already been made? Mochikit‘s test suite (Mochitest) is already a part of Mozilla’s official test suite (it’s used to test UI-specific features). I’ve already touched base with Alex Russell, of Dojo, and I’ll be working to integrate their test suite once Dojo 0.9 hits. Perhaps unsurprisingly, I’ll be working to integrate jQuery’s test suite into the core, too. Additionally, I’m also starting to contact other popular library developers attempting to get, at least, a static copy of their test suite in place.
What would you like too see? Shame we didn’t future proof $ and friends a long time ago.
Posted by Dion Almaer at 6:02 am