[Fuchsia] Improve the Fuchsia documentation.
* Move instructions about running tests from //fuchsia/README.md to
//docs/fuchsia_build_instructions.md.
* Rewrite the "Test code" section in //fuchsia/README.md to include
test guidelines and update the test code structure.
Bug: 978177
Change-Id: I43802de20a1fcb45fced1ea5ffa77b60a8566c59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1682463
Reviewed-by: Sergey Ulanov <[email protected]>
Commit-Queue: Fabrice de Gans-Riberi <[email protected]>
Cr-Commit-Position: refs/heads/master@{#674138}
diff --git a/docs/fuchsia_build_instructions.md b/docs/fuchsia_build_instructions.md
index 46d5605..fdd839ce 100644
--- a/docs/fuchsia_build_instructions.md
+++ b/docs/fuchsia_build_instructions.md
@@ -188,16 +188,15 @@
3. Add users to the "kvm" group, and have them login again, to pick-up the new
group.
-### Run test target
+### Running test suites
+
+Building test suites generate a launcher script to run them on a QEMU instance
+or a physical device. These scripts are generated at `out/fuchsia/bin`. For
+instance,to run the `base_unittests` target, launch:
```shell
$ out/fuchsia/bin/run_base_unittests
```
-This packages the built binary and test data into a disk image, and runs a QEMU
-instance from the Fuchsia SDK, outputting to the console.
-
Common gtest arguments such as `--gtest_filter=...` are supported by the run
-script.
-
-The run script also symbolizes backtraces.
+script. The launcher script also symbolizes backtraces.
