Skip to content

Latest commit

 

History

History
39 lines (30 loc) · 2.39 KB

plan_autogen.md

File metadata and controls

39 lines (30 loc) · 2.39 KB

Auto generated test plans

An auto-generated test plan is a test plan with a unique-id that is generated by parsing the WGSL specification using this tool. A typical auto-generated WGSL test plan:

g.test(<name>)
  .uniqueId(<unique-id>)
  .specURL(<url>)
  .desc(<description>)
  .params(u => u.combine('placeHolder1', ['placeHolder2', 'placeHolder3']))
  .unimplemented();
  • name: An arbitrary name.
  • url: The URL of the section this test plan is extracted from, ie. https://www.w3.org/TR/<version>/#<section-name>.section-name is the section of the WGSL specification this test plan is generated from.
  • description: The portion of WGSL specification this test plan is generated from.
  • unique-id: A token used for tracking and updating the auto generated test plans.
unique-id = sha1(<section-name> + <description>)

How to contribute

To implement an auto-generated test plan:

  1. Choose an auto-generated test plan that is not currently under development, ie. looking up the unique-id in this list must not return any results.
  2. Submit a new issue using this template. Make sure to include the unique-id and url.
  3. Implement the test plan. You may modify the test name and description; however, url and unique-id must remain unchanged.
  4. Add a comment to the issue (created in step 2) with a link to your merged pull request. Then close the issue with status Fixed.

Useful helpers

Take advantage of the helpers, specially:

Example

  • Builtin-function execution test example: abs.spec.ts.