[fuchsia] add commands for testing on Fuchsia

TESTED=ran the commands!

Change-Id: I7d8d3ca31a250005edcd3fb6269afffe8b3fbc89
Reviewed-on: https://chromium-review.googlesource.com/c/1263016
Reviewed-by: Scott Graham <scottmg@chromium.org>
This commit is contained in:
Francois Rousseau 2018-10-04 14:40:48 -07:00 committed by Scott Graham
parent ce122b644c
commit 83e37a9ac1

View File

@ -193,6 +193,13 @@ $ cd ~/crashpad/crashpad
$ python build/run_tests.py out/Debug $ python build/run_tests.py out/Debug
``` ```
To run a subset of the tests, use the --gtest\_filter flag, e.g., to run all the
tests for MinidumpStringWriter:
```sh
$ python build/run_tests.py out/Debug --gtest_filter MinidumpStringWriter*
```
### Windows ### Windows
On Windows, `end_to_end_test.py` requires the CDB debugger, installed with On Windows, `end_to_end_test.py` requires the CDB debugger, installed with
@ -220,6 +227,25 @@ variable. `run_tests.py` will upload test executables and data to a temporary
location on the detected or selected device, run them, and clean up after itself location on the detected or selected device, run them, and clean up after itself
when done. when done.
### Fuchsia
To test on Fuchsia, you need a connected device running Fuchsia and then run:
```sh
$ gn gen out/fuchsia --args='target_os="fuchsia" target_cpu="x64" is_debug=true'
$ ninja -C out/fuchsia
$ python build/run_tests.py out/fuchsia
```
If you have multiple devices running, you will need to specify which device you
want using their hostname, for instance:
```sh
$ export ZIRCON_NODENAME=scare-brook-skip-dried; \
python build/run_tests.py out/fuchsia; \
unset ZIRCON_NODENAME
```
## Contributing ## Contributing
Crashpads contribution process is very similar to [Chromiums contribution Crashpads contribution process is very similar to [Chromiums contribution