Describe how to run the Tint unit tests Change-Id: Ide29221e944175b8344ff57811578b3393a2affd Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/186544 Auto-Submit: David Neto <dneto@google.com> Reviewed-by: Ben Clayton <bclayton@google.com> Commit-Queue: Ben Clayton <bclayton@google.com>

diff --git a/docs/tint/testing.md b/docs/tint/testing.md
index ffe85de..6b9b4b9 100644
--- a/docs/tint/testing.md
+++ b/docs/tint/testing.md

@@ -6,9 +6,19 @@
   comprehensively checking functionality of internal functions and classes.
   The test code is inside the Tint source tree in files with names ending in
   `_test.cc`
+
+  To run them, build the `tint_unittests` target to produce the `tint_unittests`
+  executable, and then run the executable.
+
+  The `tint_unittests` executable supports all the standard Googletest command
+  line options, e.g. using filters to run only a subset of the tests.
+  See [Running Test Programs: Advanced
+  Options](https://google.github.io/googletest/advanced.html#running-test-programs-advanced-options)
+
 * End-to-end tests. These test the whole compiler flow, translating source
   shaders to output shaders in various languages, and optionally checking
   the text of diagnostics.  See [Tint end-to-end tests](end-to-end-tests.md).
+
 * WebGPU Conformance Test Suite (CTS). The WebGPU CTS has both validation and
   execution tests, in the `webgpu:shader` hierarchy.
   See https://github.com/gpuweb/cts