[Webkit-unassigned] [Bug 84887] New: [Navigation Timing] Import the W3C Navigation Timing test suite

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 25 12:49:52 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=84887

           Summary: [Navigation Timing] Import the W3C Navigation Timing
                    test suite
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://w3c-test.org/webperf/tests/
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Platform
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: simonjam at chromium.org
                CC: tonyg at chromium.org, sullivan at chromium.org


As discussed at the WebKit committers meeting, we should rely on upstream W3C tests instead of maintaining our own tests. Importing these tests should be an automated process. We want to build up scripts that can import all types of W3C tests. The script can pull from a local checkout of the W3 repository, so need to automate that. The imported tests should end up in http/tests/NavigationTiming/imported-w3c or something similar.

For Navigation Timing specifically, there are a few things to watch out for:

- Make sure the subresource paths are mapped correctly, even on http tests.
- Make sure that the two W3 hosts map to localhost and 127.0.0.1 correctly so that we can test cross-origin.
- Make sure they're run as text tests and not pixel tests. May need to tweak testharness.js or something.

Assuming this is done, we should be able to get rid of the webtiming-*.html tests in LayoutTests, since I believe we upstreamed all of them.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list