Remove tests that rely on undefined testing APIs #172
Comments
|
FWIW: |
|
I think at least some of those are things where the spec does define the testing API. But I agree that tests which depend on undefined browser internal APIs aren't a good fit for wpt, and vendors should find a way to run those outside of the shared suite (note that doesn't necessarily mean they can't be written to use the wpt harness and infrastructure; we have gecko-specific tests that may use gecko's internal |
Yes, that list of files certainly is superset of what is implicated in this issue (e.g., WebUSB and WebXR do define testing APIs, and are thus fine for WPT), but they are probably what needs to be audited. |
|
Has this been discussed somewhere, or are there proposed next steps? I don't think anyone who has written any of these tests is aware of this issue, and I came across it again today while looking at compute pressure, which jogged my memory. cc @past |
|
Sorry for the delay in responding here, I just saw this ping. I had reached out to the test owners and they agreed to move those tests to wpt_internal in the near term (2024) and create test APIs in the longer term (2025+). |
WPT contains a variety of tests that rely on MojoJS to run in Chromium-based browsers.
Chromium's own WPT docs say:
However, we have many cases where things are "polyfilled" via MojoJS where the spec doesn't define the testing API, and nor has there been any attempt within WPT to document what the testing API the tests expect is. (Furthermore, https://groups.google.com/a/chromium.org/g/blink-dev/search?q=mojojs makes it look like basically nobody has ever followed those steps, as nobody has done the "reach out" step.)
The tests are, thus, practically Chromium-specific, short of someone reverse-engineering what the testing API is.
For example, the Shape Detection tests that were added to WPT in web-platform-tests/wpt@dfc0080 rely on /shape-detection/resources/shapedetection-helpers.js to load testing APIs, except nowhere in https://wicg.github.io/shape-detection-api/ (or any other document) are
FaceDetectionTest,BarcodeDetectionTest, orTextDetectionTestactually defined.Notwithstanding questions of whether any such testing API would ship in the browser, this means wpt.fyi will forever show Safari as failing many of the shape detection tests, even if the feature flag were enabled by default, unless we invest in reverse-engineering Chromium's testing API. Part of the very goal of standards and WPT is to avoid vendors having to invest in reverse-engineering one-another.
In extreme, /serial/README.md even notes:
WPT cannot be a dumping ground for inherently vendor-specific tests, written with little-to-no regard for other vendors using them, as this undermines the very premise of it being a shared test suite. It is unreasonable and unhelpful for Chromium engineers to export tests which other vendors must reverse-engineer the testing API to gain any benefit from. Chromium can maintain these tests in their own, non-exported tree, and do so until such point as they define what the testing APIs actually are.
As such, we should remove all tests that rely on undefined testing APIs from WPT.
The text was updated successfully, but these errors were encountered: