tree: 0d42c4897e3fc13892faa0d1c0fd750a322a70cb [path history] [tgz]
  1. piping/
  2. readable-byte-streams/
  3. readable-streams/
  4. resources/
  5. byte-length-queuing-strategy-expected.txt
  6. byte-length-queuing-strategy.dedicatedworker-expected.txt
  7. byte-length-queuing-strategy.dedicatedworker.html
  8. byte-length-queuing-strategy.html
  9. byte-length-queuing-strategy.js
  10. byte-length-queuing-strategy.serviceworker.https-expected.txt
  11. byte-length-queuing-strategy.serviceworker.https.html
  12. byte-length-queuing-strategy.sharedworker-expected.txt
  13. byte-length-queuing-strategy.sharedworker.html
  14. count-queuing-strategy-expected.txt
  15. count-queuing-strategy.dedicatedworker-expected.txt
  16. count-queuing-strategy.dedicatedworker.html
  17. count-queuing-strategy.html
  18. count-queuing-strategy.js
  19. count-queuing-strategy.serviceworker.https-expected.txt
  20. count-queuing-strategy.serviceworker.https.html
  21. count-queuing-strategy.sharedworker-expected.txt
  22. count-queuing-strategy.sharedworker.html
  23. generate-test-wrappers.js
  24. OWNERS
  25. README.md
  26. w3c-import.log
LayoutTests/imported/w3c/web-platform-tests/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.