[Android] Add partial md documentation for instrumentation test features.

[Android] Add partial md documentation for instrumentation test features.

In particular, this documents:
 - some instrumentation test basics
 - most of the annotations

It also adds a skeletal android testing home page. This should eventually
replace //docs/android_test_instructions.md.

BUG=

Committed: https://crrev.com/5a9b37f5e88cbffda4ce7a5d821213b1b0f48849
Cr-Commit-Position: refs/heads/master@{#412398}

[jbudorick, 2016-08-16 22:49:59]

Description was changed from

==========
[Android] Add partial md documentation for instrumentation test features.

In particular, this documents:
 - some instrumentation test basics
 - most of the annotations

It also adds a skeletal android testing home page.

BUG=
==========

to

==========
[Android] Add partial md documentation for instrumentation test features.

In particular, this documents:
 - some instrumentation test basics
 - most of the annotations

It also adds a skeletal android testing home page. This should eventually
replace //docs/android_test_instructions.md.

BUG=
==========

[jbudorick, 2016-08-16 22:50:43]

jbudorick@chromium.org changed reviewers:
+ mikecase@chromium.org, rnephew@chromium.org

[mikecase (-- gone --), 2016-08-16 23:08:58]

yay! documentation! lgtm with some comments.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/index.md
File testing/android/docs/index.md (right):

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/index....
testing/android/docs/index.md:23: - [c++ browser
tests](/testing/android/docs/todo.md)
nit: alphabetize maybe? Doesnt really matter, but kinda only logical way to
organize.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
File testing/android/docs/instrumentation.md (right):

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:109: -
[`@DisabledTest`](https://chromium.googlesource.com/chromium/src/+/master/base/test/android/javatests/src/org/chromium/base/test/util/DisabledTest.java)`(msg
= "")`
s/msg/message

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:110: -
[`@FlakyTest`](https://chromium.googlesource.com/chromium/src/+/master/base/test/android/javatests/src/org/chromium/base/test/util/FlakyTest.java)`(msg
= "")`
s/msg/message

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:112: In both cases, `msg` is a message
that should describe why the test is
s/msg/message

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:118: **@DisableIf** and **Restriction**.
The **@DisableIf** annotations are intended
nit: change Restriction to @Restriction? To be consistent with everything else.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:216: #### Annotations that affect how a
test is run
super nit:

idk if it was just the markdown viewer you set up, but header4 is almost
indistinguishable from just bold **<text>**. So it makes some of these
paragraphs hard to break up, since a lot of lines start with a few bolded words.

example...

**@MinAndroidSdkLevel**
#### Annotations that affect how a test is run

^ both of these look like headers

[rnephew (Reviews Here), 2016-08-16 23:20:05]

On 2016/08/16 23:08:58, mikecase wrote:
> yay! documentation! lgtm with some comments.
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/index.md
> File testing/android/docs/index.md (right):
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/index....
> testing/android/docs/index.md:23: - [c++ browser
> tests](/testing/android/docs/todo.md)
> nit: alphabetize maybe? Doesnt really matter, but kinda only logical way to
> organize.
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
> File testing/android/docs/instrumentation.md (right):
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
> testing/android/docs/instrumentation.md:109: -
>
[`@DisabledTest`](https://chromium.googlesource.com/chromium/src/+/master/base/test/android/javatests/src/org/chromium/base/test/util/DisabledTest.java)`(msg
> = "")`
> s/msg/message
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
> testing/android/docs/instrumentation.md:110: -
>
[`@FlakyTest`](https://chromium.googlesource.com/chromium/src/+/master/base/test/android/javatests/src/org/chromium/base/test/util/FlakyTest.java)`(msg
> = "")`
> s/msg/message
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
> testing/android/docs/instrumentation.md:112: In both cases, `msg` is a message
> that should describe why the test is
> s/msg/message
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
> testing/android/docs/instrumentation.md:118: **@DisableIf** and
**Restriction**.
> The **@DisableIf** annotations are intended
> nit: change Restriction to @Restriction? To be consistent with everything
else.
> 
>
https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
> testing/android/docs/instrumentation.md:216: #### Annotations that affect how
a
> test is run
> super nit:
> 
> idk if it was just the markdown viewer you set up, but header4 is almost
> indistinguishable from just bold **<text>**. So it makes some of these
> paragraphs hard to break up, since a lot of lines start with a few bolded
words.
> 
> example...
> 
> **@MinAndroidSdkLevel**
> #### Annotations that affect how a test is run
> 
> ^ both of these look like headers

The few things I found Case already commented on, so LGTM.

[jbudorick, 2016-08-16 23:54:23]

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/index.md
File testing/android/docs/index.md (right):

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/index....
testing/android/docs/index.md:23: - [c++ browser
tests](/testing/android/docs/todo.md)
On 2016/08/16 23:08:57, mikecase wrote:
> nit: alphabetize maybe? Doesnt really matter, but kinda only logical way to
> organize.

Done.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
File testing/android/docs/instrumentation.md (right):

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:109: -
[`@DisabledTest`](https://chromium.googlesource.com/chromium/src/+/master/base/test/android/javatests/src/org/chromium/base/test/util/DisabledTest.java)`(msg
= "")`
On 2016/08/16 23:08:58, mikecase wrote:
> s/msg/message

Done.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:110: -
[`@FlakyTest`](https://chromium.googlesource.com/chromium/src/+/master/base/test/android/javatests/src/org/chromium/base/test/util/FlakyTest.java)`(msg
= "")`
On 2016/08/16 23:08:58, mikecase wrote:
> s/msg/message

Done.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:112: In both cases, `msg` is a message
that should describe why the test is
On 2016/08/16 23:08:57, mikecase wrote:
> s/msg/message

Done.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:118: **@DisableIf** and **Restriction**.
The **@DisableIf** annotations are intended
On 2016/08/16 23:08:57, mikecase wrote:
> nit: change Restriction to @Restriction? To be consistent with everything
else.

Done.

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:216: #### Annotations that affect how a
test is run
On 2016/08/16 23:08:57, mikecase wrote:
> super nit:
> 
> idk if it was just the markdown viewer you set up, but header4 is almost
> indistinguishable from just bold **<text>**. So it makes some of these
> paragraphs hard to break up, since a lot of lines start with a few bolded
words.
> 
> example...
> 
> **@MinAndroidSdkLevel**
> #### Annotations that affect how a test is run
> 
> ^ both of these look like headers

//tools/md_browser/md_browser.py (which I used locally) is definitely renders
differently than the gitiles markdown renderer. I'm going to land this as-is,
see how it looks in gitiles, and tweak it from there.

[jbudorick, 2016-08-16 23:55:15]

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
File testing/android/docs/instrumentation.md (right):

https://codereview.chromium.org/2255593002/diff/1/testing/android/docs/instru...
testing/android/docs/instrumentation.md:216: #### Annotations that affect how a
test is run
On 2016/08/16 23:54:23, jbudorick wrote:
> On 2016/08/16 23:08:57, mikecase wrote:
> > super nit:
> > 
> > idk if it was just the markdown viewer you set up, but header4 is almost
> > indistinguishable from just bold **<text>**. So it makes some of these
> > paragraphs hard to break up, since a lot of lines start with a few bolded
> words.
> > 
> > example...
> > 
> > **@MinAndroidSdkLevel**
> > #### Annotations that affect how a test is run
> > 
> > ^ both of these look like headers
> 
> //tools/md_browser/md_browser.py (which I used locally) is definitely renders
> differently than the gitiles markdown renderer. I'm going to land this as-is,
> see how it looks in gitiles, and tweak it from there.

s/is definitely renders/definitely renders/

used up my proofreading quota for the day.

[jbudorick, 2016-08-16 23:55:22]

The CQ bit was checked by jbudorick@chromium.org

[jbudorick, 2016-08-16 23:55:23]

The patchset sent to the CQ was uploaded after l-g-t-m from
mikecase@chromium.org, rnephew@chromium.org
Link to the patchset: https://codereview.chromium.org/2255593002/#ps20001
(title: "mikecase comments")

[commit-bot: I haz the power, 2016-08-16 23:56:02]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-17 00:37:01]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-17 00:38:54]

Description was changed from

==========
[Android] Add partial md documentation for instrumentation test features.

In particular, this documents:
 - some instrumentation test basics
 - most of the annotations

It also adds a skeletal android testing home page. This should eventually
replace //docs/android_test_instructions.md.

BUG=
==========

to

==========
[Android] Add partial md documentation for instrumentation test features.

In particular, this documents:
 - some instrumentation test basics
 - most of the annotations

It also adds a skeletal android testing home page. This should eventually
replace //docs/android_test_instructions.md.

BUG=

Committed: https://crrev.com/5a9b37f5e88cbffda4ce7a5d821213b1b0f48849
Cr-Commit-Position: refs/heads/master@{#412398}
==========

[commit-bot: I haz the power, 2016-08-17 00:38:55]

Patchset 2 (id:??) landed as
https://crrev.com/5a9b37f5e88cbffda4ce7a5d821213b1b0f48849
Cr-Commit-Position: refs/heads/master@{#412398}