webui: Update docs with description of new LUCI integration
Bug: 393139276
Change-Id: Ida244aae1973049e14bdb77f9320ba1a1687727c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6459928
Reviewed-by: Demetrios Papadopoulos <[email protected]>
Commit-Queue: Alex Yang <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1447822}
diff --git a/docs/webui/testing_webui.md b/docs/webui/testing_webui.md
index c2de29ac..4c776b71 100644
--- a/docs/webui/testing_webui.md
+++ b/docs/webui/testing_webui.md
@@ -352,6 +352,21 @@
that. Detailed instructions on how to use it exist in the source code
documentation [here] (https://source.chromium.org/chromium/chromium/src/+/main:chrome/test/data/webui/test_util.ts;l=107-144;drc=b1866df4398a971088ba287d4c7efe704f6bc4b1)
+### Reporting WebUI test results to LUCI
+
+WebUI test results are automatically reported to LUCI. No special handling is
+required of WebUI test authors.
+
+A single GTest typically reports a single test result. A [new test reporting
+mechanism was
+added](https://chromium-review.googlesource.com/c/chromium/src/+/6358478) to
+support reporting multiple results from a single GTest. Using this mechanism,
+each Mocha JS test can have its own entry in LUCI (see screenshot). The
+integration is accomplished by calling base::AddSubTestResult in
+WebUIMochaBrowserTest.
+
+
+
### Common errors
Tests that rely on focus, blur, or other input-related events need to be added
