Sputnik gets more tests; How compliant are the browsers?

In: web resources

16 Mar 2010

The Chromium folk have posted about JavaScript conformance as they release a test runner for Sputnik, that allows you to easily run the complete test suite from within your browser:

Sputnik touches all aspects of the JavaScript language defined in the 3rd edition of the ECMA-262 spec. In many ways it can be seen as a continuation of and a complement to existing browser conformance testing tools, such as the Acid3 test. While we are always focused on improving speed, Sputnik is not about testing how fast your browser executes JavaScript, but rather whether it does so correctly.

Since we released the Sputnik tests as an open source project, the most requested feature has been the ability to run the tests in a browser, and we are excited to launch that functionality today. The new test runner lets you run the tests from a single URL and quickly see the results in your browser. This makes it easier both for users to see how well their browser conforms to the JavaScript spec, as well as for browser makers to find bugs and incompatibilities.

You can also use Sputnik to compare browser conformance.

The dart board shows relative conformance based on the number of tests that hit or miss. Of course, in the real world, all tests are not equal. This has been an issue with Acid tests. The race to 100 is socially interesting, but if you miss a few core tests that could be worse than meeting 10 corner cases in SVG :)

Go to Source

2 Responses to Sputnik gets more tests; How compliant are the browsers?

Avatar

jonal

May 6th, 2010 at 2:29 am

C. Sputnik was launched in October 1957.
1957 was International Geophysical Year, IGY, and it was overshadowed by Russia's launch of the first artificial satellite. I was part of the Moonwatch teams when I was 16, one of thousands of amateur astronomers and others around the world who sent in tracking reports for the first satellites.
. . ..
. . . . .

Avatar

Usman Chaudhry

May 29th, 2010 at 5:17 am

High level languages are compiled and exist as straight machine code, it's sent right to the processor. Scripting languages are designed in high level languages and act as a go-between. This makes them slightly less efficient, but if you consider the fact that compiling software is time consuming, and that multiple interpreters can be written for multiple platforms each in the same (or even a different) high level language, then scripting languages start to make more sense.

Comment Form

About this blog

This blog delivers stylish and dynamic news for designers and web-developers on all subjects of design, ranging from: CSS, Ajax, Javascript, web design, graphics, typography, advertising & much more. Our goal is to help you communicate effectively on the web with an engaging website or functional interface.