[Webkit-unassigned] [Bug 187003] Add support for WPT expectation manifests

[bugzilla-daemon at webkit.org]

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

--- Comment #2 from youenn fablet <youennf at gmail.com> ---
(In reply to Frédéric Wang (:fredw) from comment #1)
> Some more references about expectation manifest:
> https://wptrunner.readthedocs.io/en/latest/expectation.html#expectation-
> manifests
> https://github.com/web-platform-tests/wpt/tree/master/tools/
> wptrunner#expectation-data
> 
> This is supported by upstream WPT but also by runners from Mozilla and
> Chromium repositories.
> 
> As mentioned in comment 0, this avoids the renaming of -ref.html =>
> -expected.html for reftests, which is causing issues like bug 186132.

This is a pain point and I agree aligning with WPT makes sense for ref tests.
We can probably generate/update the manifest at import time and use it to know whether a WPT test is a ref test or not.

We could later extend it to determine the list of WPT tests to run, but that can be done/discussed as a follow-up.

> In addition, this can also avoid the need for -expected.txt files for
> testharness.js tests (bug 82245).

I would tend to decorrelate this particular issue from the use of manifests.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180627/58c16850/attachment.html>