W3C home > Mailing lists > Public > public-webappsec@w3.org > November 2012

Re: CORS test status

From: Odin Hørthe Omdal <odinho@opera.com>
Date: Wed, 21 Nov 2012 17:38:19 +0100
Cc: bhill@paypal-inc.com
To: public-webappsec@w3.org, gopal.raghavan@nokia.com
Message-ID: <op.wn4tt5tc49xobu@odinho-fido>
On Tue, 20 Nov 2012 21:17:56 +0100, <gopal.raghavan@nokia.com> wrote:
> Sorry, I didn't have time to look through this last week.

Been busy too, story of our lives ;-)

> I noticed Odin had some checkins 2 weeks back, probably during TPAC.

Totally. Had a rage at Mercurial because I actually lost what I was doing
during some meetings. So I redid it.

> Test runner was broken, I just modified test runner to pickup changes  
> from staging.
> We have lot of regression. Test results don't look that good.
> Test results:
> Chrome; ver:23.0.1271.64; Score: 57.21%; Pass: 127; Fail: 95
> Firefox; ver: 16.0.2 Score: 53.15%; Pass: 118; Fail: 104
> Safari; ver: 6.0 (7536.25); Score: 45/50% Pass: 101; Fail: 121
> Opera; ver: 12.02; Score: 54.50%; Pass: 121; Fail: 101

Nope, I fixed quite a few errors in the testsuite. It should be okay since
two weeks ago. However, the w3c-test.org server is doing some nasty things
(like eating the OPTIONS header). I don't have SSL set up on my machine,
but you can run the testsuite there, it will pass quite a lot more than
the others.

Hmm. I'll actually send a call for review on the tests in staging now. BRB.

Pass-rate is 92%, 90%, 81% and 76%. Which is quite good.

Odin Hørthe Omdal (Velmont/odinho) · Core, Opera Software, http://opera.com
Received on Wednesday, 21 November 2012 16:39:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 November 2012 16:39:05 GMT