Move the apptest runner and parts of mopy to the public SDK.

Move the apptest runner and parts of mopy to the public SDK.

Apptest runner is useful for any party that needs to run apptests. In
particular, we want it to be available in Chromium, where html_viewer
and network service are developed.

This patch moves the apptest runner along with the relevant parts of
mopy to the public SDK. The remainings of mopy become mopy_internal.

BUG=450356

[ppi, 2015-01-27 16:40:42]

Patchset #1 (id:1) has been deleted

[ppi, 2015-01-27 17:28:45]

Patchset #1 (id:20001) has been deleted

[ppi, 2015-01-27 17:45:12]

ppi@chromium.org changed reviewers:
+ jamesr@chromium.org

[ppi, 2015-01-27 17:45:29]

Hi James,

ptal.

[jamesr, 2015-01-27 20:54:42]

jamesr@chromium.org changed reviewers:
+ msw@chromium.org

[jamesr, 2015-01-27 20:54:42]

msw@ is responsible for this (iirc) and is back from vacation next week, he
should take a look.

[jamesr, 2015-01-27 20:55:36]

jamesr@chromium.org changed reviewers:
- jamesr@chromium.org

[jamesr, 2015-01-27 20:55:36]

I don't think we should have "mopy" in the public SDK dir.  If we want to have
common utilities we should probably have somebody who knows python well design
something reasonable.  mopy is just a grab-bag of things that ended up being
useful.

[jamesr, 2015-01-27 20:55:39]

I don't think we should have "mopy" in the public SDK dir.  If we want to have
common utilities we should probably have somebody who knows python well design
something reasonable.  mopy is just a grab-bag of things that ended up being
useful.

[msw, 2015-02-04 01:47:57]

On 2015/01/27 20:55:39, jamesr wrote:
> I don't think we should have "mopy" in the public SDK dir.  If we want to have
> common utilities we should probably have somebody who knows python well design
> something reasonable.  mopy is just a grab-bag of things that ended up being
> useful.

It looks like most of what apptest_runner.py uses from mopy isn't used
elsewhere. Those files can probably be moved to the public SDK dir and
re-named/re-located specific to apptest_runner.py. The notable exceptions are
mopy/config.py and mopy/paths.py, those will have to be shared somehow between
the public SDK and our private test_runner.py (etc.), or we'll have to duplicate
that code... James do you have thoughts on duplicating or sharing those bits of
code?

I can try continuing this effort tomorrow, or you can proceed in that direction
yourself, ppi@.

[jamesr, 2015-02-04 03:09:04]

jamesr@chromium.org changed reviewers:
+ jamesr@chromium.org

[jamesr, 2015-02-04 03:09:05]

We could probably just move config.py to the public SDK and use it from
everywhere

paths.py is a bit different - it's a registry of all "important" known paths. 
This includes some paths that are in the public SDK and some that aren't, so it
can't really move wholesale to the SDK.  src_root doesn't really make sense in
the public SDK since we don't know what the root of the checkout is as that'll
vary from consumer to consumer.  What does apptest need?

[ppi, 2015-02-04 15:47:55]

This CL is not a good illustration, it was before we had working Android
support. For supporting Linux only we actually don't need much, see the simple
runner we landed for the time being in Chromium:
https://codereview.chromium.org/874273002/ .

To support Android we need mopy/android.py and this in turn depends on
//build/android/pylib for a bunch of stuff. I wrote up
https://docs.google.com/a/chromium.org/document/d/1mQlR_5bLdVxwnI_hFuLwGtk4vr...
listing the dependencies, should we move the discussion to the doc and to the
crbug?