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

Feature request: make the results available in JSON format #280

Open
mathiasbynens opened this issue May 14, 2024 · 3 comments
Open

Feature request: make the results available in JSON format #280

mathiasbynens opened this issue May 14, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@mathiasbynens
Copy link
Member

For CLIs/scripts to easily consume the results, it would be nice to make the test scores available in JSON format.

Right now webstatus.dev only includes WPT test results and arguably one could use the WPT API to compute the scores from there, but this would especially become helpful once ECMAScript/Test262 and WebAssembly test scores are reported as well.

@jcscottiii
Copy link
Collaborator

Hey @mathiasbynens, we do offer an API for our current service. It is accessible at https://api.webstatus.dev

Is this something that would work for your use-case?

On a semi-related note, it would be great to get Test262 scores into the dashboard. But we would need a way of mapping those test scores to web features. If you have any ideas, let me know. Currently, we only have the spec links from web-features. But we probably want a more concrete way.

cc: @foolip

@jcscottiii jcscottiii added the enhancement New feature or request label May 14, 2024
@foolip
Copy link
Member

foolip commented May 14, 2024

Regarding Test262, I made an attempt in web-platform-dx/web-features#1054 but found that most likely we'll also need to identify some features by path. Then we would also need results from stable browsers, which https://test262.fyi/ doesn't have.

@foolip
Copy link
Member

foolip commented May 24, 2024

See also #305 about CSV. We probably only need one format, or at least 99% of the implementation should be the same regardless of format.

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

No branches or pull requests

3 participants