| David Neto | 750120f | 2023-09-19 21:15:38 +0000 | [diff] [blame] | 1 | # Testing Tint |
| 2 | |
| 3 | Tint has multiple levels of testing: |
| 4 | |
| 5 | * Unit tests, using the Googletest framework. These are the lowest level tests, |
| 6 | comprehensively checking functionality of internal functions and classes. |
| 7 | The test code is inside the Tint source tree in files with names ending in |
| 8 | `_test.cc` |
| 9 | * End-to-end tests. These test the whole compiler flow, translating source |
| 10 | shaders to output shaders in various languages, and optionally checking |
| Jiawei Shao | b9feb09 | 2024-01-10 11:19:09 +0000 | [diff] [blame] | 11 | the text of diagnostics. See [Tint end-to-end tests](end-to-end-tests.md). |
| David Neto | 750120f | 2023-09-19 21:15:38 +0000 | [diff] [blame] | 12 | * WebGPU Conformance Test Suite (CTS). The WebGPU CTS has both validation and |
| 13 | execution tests, in the `webgpu:shader` hierarchy. |
| 14 | See https://github.com/gpuweb/cts |
| 15 | All test can be run in Chrome, and many tests can be run via `dawn.node`, |
| 16 | the [Dawn bindings for NodeJS](../../src/dawn/node/README.md). |
