Add testing section of docs

Add testing section of docs.  Consolidated trybot/buildbot section

BUG=skia:

Preview link: http://skiadocs.com:8000/dev/testing/?cl=954523004

Committed: https://skia.googlesource.com/skia/+/281bf5249c2930ff4e8a500c8c26deb8e3253b11

[hcm, 2015-02-24 05:59:50]

hcm@google.com changed reviewers:
+ borenet@google.com, jcgregorio@google.com

[hcm, 2015-02-24 06:17:35]

On 2015/02/24 05:59:50, hcm wrote:
> mailto:hcm@google.com changed reviewers:
> + mailto:borenet@google.com, mailto:jcgregorio@google.com

Please give me a proofread on the Testing section. 
Buildbot is consolidated to one page with key sections.
Ravi and I agreed to stop the migration of Cluster Telemetry for now due to lack
of public use, documentation needing updates and perhaps belonging internal or
in Chromium.
Gold will need to be added later!

[borenet, 2015-02-24 14:13:46]

Lots of comments on the buildbot section.  If you'd prefer, I can rewrite that
part, since a lot of it is old and needs updating.

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots.md
File site/dev/testing/trybots.md (right):

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:1: Skia Trybots
Are we talking about buildbots or trybots here?  I generally think of trybots as
a subset of buildbots.

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:16:
http://chromegw.corp.google.com/i/client.skia.internal/console
While these links are still useful for tracking down issues, I think it's time
to push status.skia.org as the primary view for the buildbots.

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:36: * a machine that builds and runs code as
directed by the buildbot master
More precisely, a process running on a machine.  The machine itself is the
buildslave host, and it may be running more than one buildslave process.

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:45: different builders could interfere with each
other's performance numbers
Can we move this above buildslaves (maybe to the very top) since everything is
builder-centric?  I think we could also simplify the description to something
like:

* One repeatable build and/or test configuration on a given platform.

And can we add a section for "build"?

* build

    * One run of a particular build/test configuration, at a particular code
revision

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:48: Source Code Revisions
I don't think this section is needed.  At most (if only because it bites us
whenever we land a cherry-pick on a branch), we could make a note that the Skia
code and the buildbot code are versioned independently of each other and are
only guaranteed to work properly together when both are at tip-of-tree.

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:66: Console View
Again, I think this is useful information, but I'd prefer we focus on the new UI
and treat the old console as something rarely used.

https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
site/dev/testing/trybots.md:89: Submitting a Try from Rietveld
This seems out of place here.  Maybe it belongs in a "how to create and land a
code change" doc instead?

[hcm, 2015-02-25 18:16:35]

On 2015/02/24 14:13:46, borenet wrote:
> Lots of comments on the buildbot section.  If you'd prefer, I can rewrite that
> part, since a lot of it is old and needs updating.
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots.md
> File site/dev/testing/trybots.md (right):
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:1: Skia Trybots
> Are we talking about buildbots or trybots here?  I generally think of trybots
as
> a subset of buildbots.
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:16:
> http://chromegw.corp.google.com/i/client.skia.internal/console
> While these links are still useful for tracking down issues, I think it's time
> to push http://status.skia.org as the primary view for the buildbots.
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:36: * a machine that builds and runs code as
> directed by the buildbot master
> More precisely, a process running on a machine.  The machine itself is the
> buildslave host, and it may be running more than one buildslave process.
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:45: different builders could interfere with each
> other's performance numbers
> Can we move this above buildslaves (maybe to the very top) since everything is
> builder-centric?  I think we could also simplify the description to something
> like:
> 
> * One repeatable build and/or test configuration on a given platform.
> 
> And can we add a section for "build"?
> 
> * build
> 
>     * One run of a particular build/test configuration, at a particular code
> revision
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:48: Source Code Revisions
> I don't think this section is needed.  At most (if only because it bites us
> whenever we land a cherry-pick on a branch), we could make a note that the
Skia
> code and the buildbot code are versioned independently of each other and are
> only guaranteed to work properly together when both are at tip-of-tree.
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:66: Console View
> Again, I think this is useful information, but I'd prefer we focus on the new
UI
> and treat the old console as something rarely used.
> 
>
https://codereview.chromium.org/954523004/diff/60001/site/dev/testing/trybots...
> site/dev/testing/trybots.md:89: Submitting a Try from Rietveld
> This seems out of place here.  Maybe it belongs in a "how to create and land a
> code change" doc instead?

Updated where requested, removed or moved some content... high level summary
about Status page which perhaps can be beefed up later.

[borenet, 2015-02-25 18:25:23]

Looks good! Just a couple of minor comments.

https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
File site/dev/testing/buildbot.md (right):

https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
site/dev/testing/buildbot.md:52: revision
I might slightly modify this to include "builder":  one run of a particular
builder, at a particular code revision

https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
site/dev/testing/buildbot.md:65: if the commits are on the same branch, they
will be batched into a single build.
I don't think these first two paragraphs are needed in this section.  The first
is already stated under "buildbot master" above.  If you want to keep the
second, I think we could move it after the following paragraph ("The status
view...").

[hcm, 2015-02-26 04:27:33]

https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
File site/dev/testing/buildbot.md (right):

https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
site/dev/testing/buildbot.md:52: revision
On 2015/02/25 18:25:23, borenet wrote:
> I might slightly modify this to include "builder":  one run of a particular
> builder, at a particular code revision

Done.

https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
site/dev/testing/buildbot.md:65: if the commits are on the same branch, they
will be batched into a single build.
On 2015/02/25 18:25:23, borenet wrote:
> I don't think these first two paragraphs are needed in this section.  The
first
> is already stated under "buildbot master" above.  If you want to keep the
> second, I think we could move it after the following paragraph ("The status
> view...").

Done.

[borenet, 2015-02-26 12:14:43]

On 2015/02/26 04:27:33, hcm wrote:
>
https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
> File site/dev/testing/buildbot.md (right):
> 
>
https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
> site/dev/testing/buildbot.md:52: revision
> On 2015/02/25 18:25:23, borenet wrote:
> > I might slightly modify this to include "builder":  one run of a particular
> > builder, at a particular code revision
> 
> Done.
> 
>
https://codereview.chromium.org/954523004/diff/100001/site/dev/testing/buildb...
> site/dev/testing/buildbot.md:65: if the commits are on the same branch, they
> will be batched into a single build.
> On 2015/02/25 18:25:23, borenet wrote:
> > I don't think these first two paragraphs are needed in this section.  The
> first
> > is already stated under "buildbot master" above.  If you want to keep the
> > second, I think we could move it after the following paragraph ("The status
> > view...").
> 
> Done.

LGTM

[hcm, 2015-03-02 19:19:49]

The CQ bit was checked by hcm@google.com

[commit-bot: I haz the power, 2015-03-02 19:20:01]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/954523004/120001

[commit-bot: I haz the power, 2015-03-02 19:25:29]

Committed patchset #7 (id:120001) as
https://skia.googlesource.com/skia/+/281bf5249c2930ff4e8a500c8c26deb8e3253b11