{"id":827,"date":"2023-01-20T12:05:08","date_gmt":"2023-01-20T03:05:08","guid":{"rendered":"https:\/\/blogs.igalia.com\/gyuyoung\/?p=827"},"modified":"2023-01-20T12:05:08","modified_gmt":"2023-01-20T03:05:08","slug":"webgpu-conformance-test-suite","status":"publish","type":"post","link":"https:\/\/blogs.igalia.com\/gyuyoung\/2023\/01\/20\/webgpu-conformance-test-suite\/","title":{"rendered":"WebGPU Conformance Test Suite"},"content":{"rendered":"\n\n

WebGPU<\/strong> Introduction<\/h2>\n\n\n\n\nWebGPU is a new Web API that exposes modern computer graphics capabilities, specifically Direct3D 12, Metal, and Vulkan, for performing rendering and computation operations on a GPU. This goal is similar to the WebGL<\/a> family of APIs, but WebGPU enables access to more advanced features of GPUs. Whereas WebGL is mostly for drawing images but can be repurposed (with great effort) for other kinds of computations, WebGPU provides first-class support for performing general computations on the GPU. \n\n\n\nIn other words, the WebGPU API is the successor to the WebGL and WebGL2 graphics APIs for the Web. It provides modern features such as \u201cGPU compute\u201d as well as lower overhead access to GPU hardware and better, more predictable performance. The below picture shows the WebGPU architecture diagram simply.[1]
\n\n\n\n
\"\"<\/figure>\n\n\n\n\n

WebGPU CTS<\/strong><\/h2>\n\n\n\n\nThere is currently a CTS (Conformance Test Suites) that tests the behaviors defined by the WebGPU specification. The CTS has been written in TypeScript and developed in GitHub<\/a>, and the CTS can be run with a sort of ‘adapter layer’ to work under other test infrastructures like WPT and Telemetry. At this point, there are around 1,400 tests that check the validation and operation of WebGPU implementations.\n\n\n\nThere is a site to run the WebGPU CTS. If you go to the URL below with a browser that enables the WebGPU feature, you can run the CTS on your browser.\n\n\n\n https:\/\/gpuweb.github.io\/cts\/standalone\/?runnow=0&worker=0&debug=0&q=webgpu:<\/a><\/em>
\n\n\n\n\n

Contribution<\/strong><\/h2>\n\n\n\n\nThe WebGPU CTS has progressed in GitHub. If you want to contribute to the CTS project, you can start by taking a look at the issues<\/a> that have been filed. Please follow the sequence below:\n\n\n\n\n
  1. Set up the CTS developing environment.<\/li>
  2. Add to or edit the test plan in the CTS project site.<\/li>
  3. Implement the test.<\/li>
  4. Upload the test and request a review.<\/li><\/ol>\n\n\n\n\n\n

    Organization<\/h2>\n\n\n\n\nThe CTS is largely composed of four categories – API<\/strong>, Shader<\/strong>, IDL<\/strong>, and Web Platform<\/strong>. First, the API<\/strong> category tests full coverage of the Javascript API surface of WebGPU. The Shader<\/strong> category tests the full coverage of the shaders that can be passed to WebGPU. The IDL<\/strong> category checks that the WebGPU IDL is correctly implemented. Lastly, the Web Platform<\/strong> category tests WebPlatform-specific interactions.\n\n\n\n\n

    Example<\/h2>\n\n\n\n\nThis is a simple test<\/a> for checking writeBuffer function validation. Basically, a general test consists of three blocks like description<\/strong>, parameters<\/strong>, and function body<\/strong>.\n\n\n\n
    \"\"<\/figure>\n\n\n\n\n