Google Chrome has been released 2 weeks ago: it's still beta. But, according to the comics issues for the launch, a huge emphasis was put on testing for maximum quality at launch: rendering of milions of pages is validated for each build. At page 11,a progressive improvement from 23% (early days) to 99% (launch date) in the Webkit layout testing suite is stated as a proof of quality.
I am used to working with 2 of them: YUI (currently at v2.5.2) and Prototype/script.aculo.us (currently at v1.8.1). Both of them are delivered with a series of unit tests. I decided to run Google Chrome against those suits to see what would happen.
The results are the followings:
with Script.aculo.us 1.8.1:
with Yahoo YUI 2.5.2:
Various conclusions could be drawn from that point knowing that no adaptation was yet made in the 2 frameworks to cope specifically with "specialties" of Chrome:
- Chrome fails on 74 tests out of 700. Success rate is already above 89%
- More careful analysis proves that 50 of those failures come from a single area: cookie handling in YUI. I will now analyze source code of YUI cookie.js to get all details: but it's probably just a few lines of codes to modify to pass those tests. When that will be done success rate will jump already above 96%
- globally, it's very reassuring to see that issues are confined to a very limited number of areas and not spread all over the place.
Using the bundled suite of 114 tests named named yuitest.html and part of YUI, we get the following results:
- 10s for Firefox 220.127.116.11
- 6s for IE 18.104.22.168C0
- 2s for Google Chrome 0.2.149.29
Source: blog Media & Tech (par didier durand)