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.

Sign up for GitHub

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

Jump to bottom

Add links to relevant web platform tests #354

Open
domenic opened this issue Nov 23, 2015 · 8 comments
Open

Add links to relevant web platform tests #354

domenic opened this issue Nov 23, 2015 · 8 comments
Labels
spec tooling

Comments

@domenic
Copy link
Member

domenic commented Nov 23, 2015

I had a fun idea. To supplement can i use data, which is fairly coarse-grained, we could also link to web-platform-test results.

These could be correlated with section IDs via either the folder structure of web platform tests, or the <link rel="help"> links which are sporadically found in the <head>.

I'm not sure exactly what we would link to. E.g. would http://w3c-test.org/html/browsers/browsing-the-web/navigating-across-documents/ be good, even though it's just a directory listing? Or are there better test reports out there, perhaps ones that show the results in all the latest browsers?

Anyway, wanted to get this idea out there for discussion.
@zcorpan
Copy link
Member

zcorpan commented Nov 23, 2015

Check out what bikeshed does for CSS specs

@foolip
Copy link
Member

foolip commented Jan 26, 2016

This would be great. Since wpt is supposed to use section IDs as directory names, it would probably be possible to write a tool to automatically associate tests with sections, and then just tweak either HTML or wpt until everything shows up where it's supposed to.

What does Bikeshed do?

@zcorpan
Copy link
Member

zcorpan commented Jan 26, 2016

cc @tabatkins @plinss

@zcorpan
Copy link
Member

zcorpan commented Jan 26, 2016

Note that <link rel=help href=...> is also used in wpt, and test() or async_test() can also pass metadata with spec links, e.g. https://github.com/w3c/web-platform-tests/blob/f685409553687752d593a435e56f87f4094c0fd9/html/semantics/forms/the-input-element/search_input.html#L27

@Ms2ger
Copy link
Member

Ms2ger commented Jan 29, 2016

The argument to the test functions is mostly dead cruft, in my experience.

@plinss
Copy link

plinss commented Jan 29, 2016

Bikeshed uses the Shepherd API to discover CSS test suites and injects a line of script that adds annotations to the spec listing test results at each section heading where tests are present in the test suite (and a summary at the top). The test results link to the CSS test harness.

Shepherd also has an API to map spec anchors to specific spec sections.

The test data is taken from the CSS test harness: http://test.csswg.org/harness/

For an example, see: https://drafts.csswg.org/css-flexbox/

If there's an API to get similar test data for the WPT tests, then we could add this functionality (FWIW, the CSS specs/tests have had this functionality for years, it's one of the reasons we require spec links in tests).

@annevk
Copy link
Member

annevk commented May 3, 2017

I suggest we close this as it doesn't really seem feasible. Also, newer WPT tests don't have a clear way of linking to specification text.

@domenic
Copy link
Member Author

domenic commented May 3, 2017

Why do you think this isn't feasible? The directory structure alone could help, much less the link rel="help"s.

@foolip foolip mentioned this issue Sep 6, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec tooling
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Ms2ger @zcorpan @foolip @domenic @annevk @plinss