Documentation: Mention need to flash your device for Android tests.
Change-Id: I5b4035dadf55b3a5e1d1b32010f0bfd324ad9b6b Reviewed-on: https://chromium-review.googlesource.com/c/1355313 Reviewed-by: agrieve <agrieve@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#612993}
This commit is contained in:

committed by
Commit Bot

parent
b35a59e14e
commit
3473e2ed17
@ -6,6 +6,19 @@
|
||||
|
||||
### Physical Device Setup
|
||||
|
||||
#### Root Access
|
||||
|
||||
Running tests requires being able to run "adb root", which requires using a
|
||||
userdebug build on your device.
|
||||
|
||||
To use a userdebug build, see
|
||||
[Running Builds](https://source.android.com/setup/build/running.html). Googlers
|
||||
can refer to [this page](https://goto.google.com/flashdevice).
|
||||
|
||||
If you can't run "adb root", you will get an error when trying to install the
|
||||
test APKs like "adb: error: failed to copy" and "remote secure_mkdirs failed:
|
||||
Operation not permitted".
|
||||
|
||||
#### ADB Debugging
|
||||
|
||||
The adb executable exists within the Android SDK:
|
||||
|
Reference in New Issue
Block a user