W3C home > Mailing lists > Public > public-test-infra@w3.org > October to December 2011

[Bug 14839] New: Separate WebKit into Safari and Chrome

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 Nov 2011 09:44:31 +0000
To: public-test-infra@w3.org
Message-ID: <bug-14839-4828@http.www.w3.org/Bugs/Public/>

           Summary: Separate WebKit into Safari and Chrome
           Product: Testing
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Test Framework
        AssignedTo: mike@w3.org
        ReportedBy: tonyg@chromium.org
         QAContact: dave.null@w3.org
                CC: public-test-infra@w3.org

For the Navigation Timing tests, it is not accurate to group Safari and Chrome
into one WebKit engine.

The summary page makes it look like WebKit often fails the tests:

However, drilling into one test it becomes clear what is going on:

All Chrome runs pass and all Safari runs fail.

So the test result is really just indicating whether the test was run more
often in Safari or Chrome. This needs to be fixed to separate them out. I
suggest columns "WebKit (Safari)" and "WebKit (Chrome)". WebKit variants other
than Safari/Chrome should be sufficiently rare to discard.

I suspect this may be true for test suites other than Navigation Timing, but
haven't verified. Very often there is browser code outside of WebKit that is
necessary to support web platform APIs. It is also very common to have flag
guards to enable/disable web platform APIs in WebKit.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 16 November 2011 09:44:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:32 UTC