Philip Jägenstedt
Philip Jägenstedt
I found the prior work/discussions that I vaguely remembered: - https://github.com/web-platform-tests/wpt/issues/8308 - https://github.com/web-platform-tests/wpt/pull/8980 - https://github.com/web-platform-tests/wpt/issues/19438 @annevk and @jgraham were somewhat involved with that.
Having looked at https://github.com/web-platform-tests/wpt/pull/8980, I think a path forward here could be: - Revive https://github.com/web-platform-tests/wpt/pull/8980. This will require an RFC, and I expect discussion about how to make these tests...
Given how many tests there are I'd also prefer to not check them in. That also avoids license questions. It would make more sense to me as either a build...
I've tried reviving the previous attempt in https://github.com/web-platform-tests/wpt/pull/35621. It doesn't work yet, tests fail because `assert` isn't defined.
Interop 2023 launched yesterday, and we ended up not needing any integration with Test262.
We didn't have any proposals in Interop 2024 that needed Test262, and we didn't start an investigation effort for it. We did however start an investigation effort for WebAssembly testing,...
Something like https://wpt.fyi/results/?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2024-indexeddb%20status%3Aerror is a small subset of such a query, currently reveling a harness error in Chrome.
@zcorpan any thoughts on how to implement this? The labels are in https://github.com/web-platform-tests/wpt-metadata and can be accessed via a wpt.fyi API. Either would be an external dependency which would increase...
Looks like the API is undocumented (https://github.com/web-platform-tests/wpt.fyi/issues/3337) but one can get all of the labels in a single API call at https://wpt.fyi/api/metadata?product=chrome&includeTestLevel. Whether using that API or a clone of...