Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(149)

Side by Side Diff: docs/android_test_instructions.md

Issue 1351233003: [Docs] Fix shell command formatting and line breaking (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Android Test Instructions 1 # Android Test Instructions
2 2
3 Device Setup Tests are runnable on physical devices or emulators. See the 3 Device Setup Tests are runnable on physical devices or emulators. See the
4 instructions below for setting up either a physical device or an emulator. 4 instructions below for setting up either a physical device or an emulator.
5 5
6 [TOC] 6 [TOC]
7 7
8 ## Physical Device Setup **ADB Debugging** 8 ## Physical Device Setup **ADB Debugging**
9 9
10 In order to allow the ADB to connect to the device, you must enable USB 10 In order to allow the ADB to connect to the device, you must enable USB
(...skipping 114 matching lines...) Expand 10 before | Expand all | Expand 10 after
125 out\_android, then do `export CHROMIUM_OUT_DIR=out_android` before running the 125 out\_android, then do `export CHROMIUM_OUT_DIR=out_android` before running the
126 command below. 126 command below.
127 127
128 ## INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE 128 ## INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE
129 129
130 If you see this error when test\_runner.py is attempting to deploy the test 130 If you see this error when test\_runner.py is attempting to deploy the test
131 binaries to the AVD emulator, you may need to resize your userdata partition 131 binaries to the AVD emulator, you may need to resize your userdata partition
132 with the following commands: 132 with the following commands:
133 133
134 ```shell 134 ```shell
135 # Resize userdata partition to be 1G resize2fs 135 # Resize userdata partition to be 1G
136 android_emulator_sdk/sdk/system-images/android-19/x86/userdata.img 1G 136 resize2fs android_emulator_sdk/sdk/system-images/android-19/x86/userdata.img 1G
137 137
138 # Set filesystem parameter to continue on errors; Android doesn't like some 138 # Set filesystem parameter to continue on errors; Android doesn't like some
139 # things e2fsprogs does. 139 # things e2fsprogs does.
140 tune2fs -e continue 140 tune2fs -e continue android_emulator_sdk/sdk/system-images/android-19/x86/userda ta.img
141 android_emulator_sdk/sdk/system-images/android-19/x86/userdata.img
142 ``` 141 ```
143 142
144 ## Symbolizing Crashes 143 ## Symbolizing Crashes
145 144
146 Crash stacks are logged and can be viewed using adb logcat. To symbolize the 145 Crash stacks are logged and can be viewed using adb logcat. To symbolize the
147 traces, pipe the output through 146 traces, pipe the output through
148 `third_party/android_platform/development/scripts/stack`. If you build in an 147 `third_party/android_platform/development/scripts/stack`. If you build in an
149 output directory other than "out", pass 148 output directory other than "out", pass
150 `--chrome-symbols-dir=out_directory/{Debug,Release}/lib` to the script as well. 149 `--chrome-symbols-dir=out_directory/{Debug,Release}/lib` to the script as well.
151 150
(...skipping 103 matching lines...) Expand 10 before | Expand all | Expand 10 after
255 See 254 See
256 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tes ts 255 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tes ts
257 256
258 ## Running GPU tests 257 ## Running GPU tests
259 258
260 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall) 259 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
261 260
262 See http://www.chromium.org/developers/testing/gpu-testing for details. Use 261 See http://www.chromium.org/developers/testing/gpu-testing for details. Use
263 --browser=android-content-shell. Examine the stdio from the test invocation on 262 --browser=android-content-shell. Examine the stdio from the test invocation on
264 the bots to see arguments to pass to src/content/test/gpu/run\_gpu\_test.py. 263 the bots to see arguments to pass to src/content/test/gpu/run\_gpu\_test.py.
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698