0

crosier: add debugging section to the Crosier development guide.

Bug: b:294097177
Change-Id: Iaa65c99a25b3dce50ebeac91f8b65efaf08bd6ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515234
Commit-Queue: Alex Bergman <abergman@google.com>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Sven Zheng <svenzheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1300993}
This commit is contained in:
Alex Bergman
2024-05-15 00:08:09 +00:00
committed by Chromium LUCI CQ
parent e19ca0ba5c
commit 098d616775

@@ -28,6 +28,13 @@ Each Crosier test being added should include test metadata in `yaml` format.
See [Crosier metadata guide](https://source.chromium.org/chromium/chromium/src/+/main:docs/testing/chromeos_integration/crosier_metadata.md)
for more information on how to add it.
## Debugging Crosier tests
Debugging a Crosier test is like debugging any Chrome test on device. Following
developer library resources are available:
https://www.chromium.org/chromium-os/developer-library/guides/#debugging
## Continuous builders
Currently the test binary runs against both Ash and Lacros on CI only.