tree: 90154f47e0fb57d44203924961180bde3fa3a516 [path history] [tgz]
  1. piping/
  2. readable-byte-streams/
  3. readable-streams/
  4. resources/
  5. writable-streams/
  6. byte-length-queuing-strategy.dedicatedworker.html
  7. byte-length-queuing-strategy.html
  8. byte-length-queuing-strategy.js
  9. byte-length-queuing-strategy.serviceworker.https.html
  10. byte-length-queuing-strategy.sharedworker.html
  11. count-queuing-strategy.dedicatedworker.html
  12. count-queuing-strategy.html
  13. count-queuing-strategy.js
  14. count-queuing-strategy.serviceworker.https.html
  15. count-queuing-strategy.sharedworker.html
  16. generate-test-wrappers.js
  17. OWNERS
  18. README.md
third_party/WebKit/LayoutTests/external/wpt/streams/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.html
  • count-queueing-strategy.dedicatedworker.html
  • count-queueing-strategy-sharedworker.html
  • count-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.