Android: add documentation about junit tests.

docs/android_test_instructions.md

Index: docs/android_test_instructions.md
diff --git a/docs/android_test_instructions.md b/docs/android_test_instructions.md
index 2129cadde9166cfc8effa383f2ec092c745bde4c..dc8c321a73562476ee4a196b0f9e46f5fd022432 100644
--- a/docs/android_test_instructions.md
+++ b/docs/android_test_instructions.md
@@ -124,7 +124,9 @@ If you build in an output directory other than "out", you may have to tell
 test\_runner.py where you place it. Say you build your android code in
 out\_android, then do `export CHROMIUM_OUT_DIR=out_android` before running the
 command below. You have to do this even if your "out" directory is a symlink
-pointing to "out_android".
+pointing to "out_android". You can also use ```--output-directory``` to point
+to the path of your output directory, for example,
+```--output-directory=out_android/Debug```.
 
 ## INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE
 
@@ -149,6 +151,33 @@ traces, pipe the output through
 output directory other than "out", pass
 `--chrome-symbols-dir=out_directory/{Debug,Release}/lib` to the script as well.
 
+## 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```.
+
+When adding a new JUnit test, the associated ```BUILD.gn``` file must be updated
+. For example, adding a test to ```chrome_junit_tests``` requires to update

[Bernhard Bauer, 2015/10/23 15:20:21]

Does this work, or do you get a space before the period?

[mlamouri (slow - plz ping), 2015/10/26 11:12:18]

It works.

+```chrome/android/BUILD.gn```. If you are a GYP user, you will not need to do
+that step in order to run the test locally but it is still required for GN users
+to run the test.
+
+```shell
+# Build the test suite.
+ninja -C out/Release chrome_junit_tests

[dgn, 2015/10/26 10:12:05]

Why do you demo it with a release build? Aren't we supposed to do dev work on
Debug?

[mlamouri (slow - plz ping), 2015/10/26 11:12:18]

Consistency with the rest of the documentation. We can change the entire
document if needed.

+
+# Run the test suite.
+build/android/test_runner.py junit -s chrome_junit_tests --release -vvv
+
+# Run a subset of tests. You might need to pass the package name for some tests.
+build/android/test_runner.py junit -s chrome_junit_tests --release -vvv
+-f "org.chromium.chrome.browser.media.*"
+```
+
 ## Gtests
 
 ```shell