Run App tests on Android.

Run App tests on Android.

Also refactor os selector in mojo/tools/data/apptests and
mojo/tools/data/unittests

R=viettrungluu@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/b96671e5ba978bfd00782de28832025ead0be842

[qsr, 2015-01-28 11:37:46]

Trung, gentle ping?

[viettrungluu, 2015-01-28 18:32:44]

Hmmm, I like making test_runner.py also get the Config from GN args.

I don't think adding another ad hoc field to the test list.

Instead, how about we:
* exec the test list data instead of eval-ing it
* in doing so, expose the config to the execution context
* have the "test list data" set (or append to) a test_list variable (which we
examine afterwards)

[qsr, 2015-01-28 18:33:50]

On 2015/01/28 18:32:44, viettrungluu wrote:
> Hmmm, I like making test_runner.py also get the Config from GN args.
> 
> I don't think adding another ad hoc field to the test list.
> 
> Instead, how about we:
> * exec the test list data instead of eval-ing it
> * in doing so, expose the config to the execution context
> * have the "test list data" set (or append to) a test_list variable (which we
> examine afterwards)

 Can we do this in a follow up CL? I'd like to start running tests on Android. I
will work on this just after?

[viettrungluu, 2015-01-28 22:01:16]

On 2015/01/28 18:33:50, qsr wrote:
> On 2015/01/28 18:32:44, viettrungluu wrote:
> > Hmmm, I like making test_runner.py also get the Config from GN args.
> > 
> > I don't think adding another ad hoc field to the test list.
> > 
> > Instead, how about we:
> > * exec the test list data instead of eval-ing it
> > * in doing so, expose the config to the execution context
> > * have the "test list data" set (or append to) a test_list variable (which
we
> > examine afterwards)
> 
>  Can we do this in a follow up CL? I'd like to start running tests on Android.
I
> will work on this just after?

OK, LGTM then (even if you'll just end up deleting a bunch of stuff you're
adding in this CL).

[qsr, 2015-01-29 10:05:58]

Committed patchset #2 (id:20001) manually as
b96671e5ba978bfd00782de28832025ead0be842 (presubmit successful).