Industry Javascript Standards Test Available
blogs.msdn.com
blogs.msdn.com
The reason I like this competitive, evolving style of tests is simple: it's much harder to design a browser to the test, rather than the standard. With, say, the Acid test, browsers build in the specific functionality that it tests, which results is very un-even standards compliance and altogether mis-representative test results. If it's not on the test, vendors drag their feet on implementing. With this new style, if there's any part of the standard that browsers haven't implemented, one vendor can implement it, and contribute tests around it. Now they can show how they're more standards-compliant, and everyone else will catch up because they're being tested on it. This competition encourages all the vendors to a) implement the full breadth of the standard b) contribute tests cover the full breadth of the standard. Win-win for users.
The test262 suite was actually published by the ECMA international standards body, although Microsoft did contribute their tests.
The direct link to the suite is http://test262.ecmascript.org/
And the announcement from ECMA international is at http://www.ecma-international.org/news/PressReleases/PR_ISOI...