Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENHANCEMENT] show support percentage for TC39 features via test262 result data #490

Open
michaelficarra opened this issue Jul 3, 2024 · 3 comments
Labels
blocked:upstream-data Blocked on correcting or adding upstream data enhancement New feature or request

Comments

@michaelficarra
Copy link

Where some features show support percentages, features defined by TC39 show this message:

image

Show the test262 pass percentage for the feature instead. All TC39 proposals have an associated test262 feature flag so that you can collect all the tests. See https://test262.fyi/, a website that does this already.

image
@michaelficarra michaelficarra added the enhancement New feature or request label Jul 3, 2024
@past
Copy link
Collaborator

past commented Jul 8, 2024

web-platform-tests/interop#117 is relevant here. @foolip is it better to wait for an Interop-endorsed approach here or can WebDX provide test262 annotations for Web Features?

@foolip
Copy link
Member

foolip commented Jul 8, 2024

I previously took a look at using test262.fyi results, and @CanadaHonk kindly helped expose some data that would be useful for this is in test262-fyi/test262.fyi#51. The biggest issue is that there's no data corresponding to stable releases of browsers, and that is what we show by default on webstatus.dev. (For experimental we could use V8 results for Chrome+Edge, SpiderMonkey for Firefox, and JavaScriptCore for Safari.)

I think that Test262 results from the same browser binaries that show up on wpt.fyi would be the most useful. Something like web-platform-tests/wpt#8980 / web-platform-tests/wpt#35621 is on way to go about it that I think is promising. An alternative path would be to run set up real browsers for test262.fyi and use those results. That might in fact be easier, but I'm not as familiar with what it would take.

@jcscottiii jcscottiii added the blocked:upstream-data Blocked on correcting or adding upstream data label Jul 16, 2024
@foolip
Copy link
Member

foolip commented Jul 30, 2024

https://github.com/tc39/test262/blob/main/features.txt is the file in Test262 defining feature identifiers, which are then used in tests. That's what gets surfaced on test262.fyi, IIUC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked:upstream-data Blocked on correcting or adding upstream data enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

4 participants