Fix the android symbolization instructions.

docs/android_test_instructions.md

 # Android Test Instructions
 
 Device Setup Tests are runnable on physical devices or emulators. See the
 instructions below for setting up either a physical device or an emulator.
 
 [TOC]
 
 ## Physical Device Setup **ADB Debugging**
 
 In order to allow the ADB to connect to the device, you must enable USB
@@ skipping 134 matching lines @@
 # Set filesystem parameter to continue on errors; Android doesn't like some
 # things e2fsprogs does.
 tune2fs -e continue android_emulator_sdk/sdk/system-images/android-23/x86/userdata.img
 ```
 
 ## Symbolizing Crashes
 
 Crash stacks are logged and can be viewed using adb logcat. To symbolize the
 traces, pipe the output through
 `third_party/android_platform/development/scripts/stack`. If you build in an
-output directory other than "out", pass
-`--chrome-symbols-dir=out_directory/{Debug,Release}/lib` to the script as well.
+output directory other than "out/{Debug,Release}", pass
+`--chrome-symbols-dir=out_path` to the script as well.

[agrieve, 2015/12/18 20:19:33]

I think you should give explicit examples for both GYP and GN, since with
--chrome-symbols-dir, you need to pass it out/Debug/lib on GYP and
out/Debug/lib.unstripped for GN.

Alternatively, it's might be better to do promote the use of:
CHROMIUM_OUTPUT_DIR=path/to/out/Debug
third_party/android_platform/development/scripts/stack

since then the script will look for both lib and lib.unstripped within there.

[Jeffrey Yasskin, 2015/12/18 21:00:06]

How's this?

 
 ## JUnit tests
 
 JUnit tests are Java unittests running on the host instead of the target device.
 They are faster to run and therefore are recommended over instrumentation tests
 when possible.
 
 The JUnits tests are usually following the pattern of *target*\_junit\_tests,
 for example, `content_junit_tests` and `chrome_junit_tests`.
 
@@ skipping 121 matching lines @@
 See
 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests
 
 ## Running GPU tests
 
 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
 
 See http://www.chromium.org/developers/testing/gpu-testing for details. Use
 --browser=android-content-shell. Examine the stdio from the test invocation on
 the bots to see arguments to pass to src/content/test/gpu/run\_gpu\_test.py.