forked from mirrors/gecko-dev
ad15893d3d
Automatic update from web-platform-testsRename of OWNER files to META.yml -- wpt-commits: e600ea2e919641566238cef57ff59f1ee21e50d3 wpt-pr: 11201 |
||
|---|---|---|
| .. | ||
| piping | ||
| readable-byte-streams | ||
| readable-streams | ||
| resources | ||
| transform-streams | ||
| writable-streams | ||
| byte-length-queuing-strategy.dedicatedworker.html | ||
| byte-length-queuing-strategy.html | ||
| byte-length-queuing-strategy.js | ||
| byte-length-queuing-strategy.serviceworker.https.html | ||
| byte-length-queuing-strategy.sharedworker.html | ||
| count-queuing-strategy.dedicatedworker.html | ||
| count-queuing-strategy.html | ||
| count-queuing-strategy.js | ||
| count-queuing-strategy.serviceworker.https.html | ||
| count-queuing-strategy.sharedworker.html | ||
| generate-test-wrappers.js | ||
| META.yml | ||
| README.md | ||
Streams Tests
The work on the streams tests is closely tracked by the specification authors, who maintain a reference implementation intended to match the spec line-by-line while passing all of these tests. See the whatwg/streams repository for details. Some tests may be in that repository while the spec sections they test are still undergoing heavy churn.
Generating wrapper files
Because the streams feature is supposed to work in all global contexts, each test is written as a .js file, and then four .html files are generated around it. So for example, for count-queueing-strategy.js, we have the wrapper files:
count-queueing-strategy.https.htmlcount-queueing-strategy.dedicatedworker.htmlcount-queueing-strategy-sharedworker.htmlcount-queueing-strategy-serviceworker.html
These are generated automatically by the Node.js script in generate-test-wrappers.js. See it for details, and please remember to use it whenever adding new tests.