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
Docs: JavaScript tests #24903
Docs: JavaScript tests #24903
Conversation
This tries to pull some of the more pertinent content forward. TODO: * create more links into testharness-api * figure out how to weave in testdriver.js references * rewrite idlharness to account for all the changes to how we do that today Feedback appreciated.
6303ae8
to
7e9c6ce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally the testharness.js docs changes lgtm; I didn't read the idlharness ones as closely since others use that more than me,
|
||
Use `// META: timeout=long` at the beginning of the resource. | ||
|
||
### Specifying test [variants](#variants) in auto-generated boilerplate tests | ||
### Specifying test [variants](#variants) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a little odd to mention variants here before they're introduced below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I make it part of the variants section somehow? It definitely seems better to have variants listed later on.
Thanks, I hope @stephenmcgruer can review the IDL part. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I like the change overall and just have some nitpicky/optional suggestions.
This page describes testharness.js exhaustively; [the tutorial on writing a | ||
testharness.js test](testharness-tutorial) provides a concise guide to writing | ||
a test--a good place to start for newcomers to the project. | ||
## Window tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see how this might be a more logical structure for test authors! As a tooling/infra maintainer, I always think of it as "I write the test page" vs. "server generates the test page" on the top level.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, server documentation is still suboptimal and might warrant another look to ensure common patterns are covered adequately.
I plan on merging this tomorrow. Let me know if you need more time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IDL section LGTM with two non-blocking suggestions
Thanks @stephenmcgruer for highlighting that. I created #25327, #25331, #25334, #25353, #25354, #25355, and #25356, as well as some PRs that are already merged, to convince myself that we have no need for those methods and everything we have can be done with I'll give this another day before merging given the changes I just made to tighten up the idlharness documentation. |
The one instance I forgot about is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still LGTM - thanks for going the extra mile here!
This tries to pull some of the more pertinent content forward.
TODO:rewrite idlharness to account for all the changes to how we do that todayFeedback appreciated.