Use named automation interface to control primary chrome on ChromeOS

Use named automation interface to control the primary chrome to run pyauto-based chrome tests on ChromeOS.

This CL includes:
  - enable_testing.py -- sends dbus call to session_manager to enable testing interface
  - pyauto.py -- integration of named automation interface with PyAuto
  - desktopui_PyAutoFunctionalTests.py -- setup to use named automation interface.  Uses a suid-root binary (as discussed with cmasone) to dbus mesg to session_manager
  - PYAUTO_TESTS -- a new suite called "PRIMARY_CHROME" which currently consists of a basic hello world test that controls the primary chrome
  - chromeos_basic.py -- a basic test

All plumbing necessary to integrate the named automation interface with autotest and pyauto is included.
It's designed such that it's easy to work directly on a chromeos device while adding/editing a pyauto test, without having to run via autotest every time.  Also, the existing pyauto tests (about 200 of them) will begin controlling the primary chrome.

Can be run with run_remote_tests.sh as:
  $ ./run_remote_tests.sh --remote <IP> desktopui_PyAutoFunctionalTests

BUG=
TEST=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=75797

[Nirnimesh, 2011-02-19 00:29:55]

I'm adding only one test to begin with for the named automation interface.
I'll migrate all the existing pyauto tests to this suite after verifying them
one by one.

[Chris Masone, 2011-02-22 15:58:41]

http://codereview.chromium.org/6410134/diff/11001/chrome/test/chromeos/autote...
File
chrome/test/chromeos/autotest/files/client/site_tests/desktopui_PyAutoFunctionalTests/desktopui_PyAutoFunctionalTests.py
(right):

http://codereview.chromium.org/6410134/diff/11001/chrome/test/chromeos/autote...
chrome/test/chromeos/autotest/files/client/site_tests/desktopui_PyAutoFunctionalTests/desktopui_PyAutoFunctionalTests.py:33:
shutil.copy('/usr/local/bin/python2.6', suid_python)
Shouldn't this copy of python be deleted after the test?  And isn't it brittle
to copy /usr/local/bin/python2.6?  A change to the location or version will
break all these tests.

http://codereview.chromium.org/6410134/diff/11001/chrome/test/chromeos/autote...
chrome/test/chromeos/autotest/files/client/site_tests/desktopui_PyAutoFunctionalTests/desktopui_PyAutoFunctionalTests.py:43:
utils.system(login_cmd)
seems like pretty much all the above should be in initialize()

http://codereview.chromium.org/6410134/diff/11001/chrome/test/pyautolib/chrom...
File chrome/test/pyautolib/chromeos/enable_testing.py (right):

http://codereview.chromium.org/6410134/diff/11001/chrome/test/pyautolib/chrom...
chrome/test/pyautolib/chromeos/enable_testing.py:37: '', '--extra-chrome-flags',
action='append', default=[],
What are these flags expected to be?  Adding and removing command line flags
isn't really supported on chrome os, except by about:flags.

[Nirnimesh, 2011-02-22 22:17:18]

http://codereview.chromium.org/6410134/diff/11001/chrome/test/chromeos/autote...
File
chrome/test/chromeos/autotest/files/client/site_tests/desktopui_PyAutoFunctionalTests/desktopui_PyAutoFunctionalTests.py
(right):

http://codereview.chromium.org/6410134/diff/11001/chrome/test/chromeos/autote...
chrome/test/chromeos/autotest/files/client/site_tests/desktopui_PyAutoFunctionalTests/desktopui_PyAutoFunctionalTests.py:33:
shutil.copy('/usr/local/bin/python2.6', suid_python)
On 2011/02/22 15:58:41, Chris Masone wrote:
> Shouldn't this copy of python be deleted after the test?

I thought about that but decided that it'd be convenient to hack on the machine
while working on editing test scripts if all the setup remains there after a
test is run.
This is in keeping with autotest setups -- you run once and then can hack on the
machine. All autotest tests begin with a clean /usr/local/autotest dir anyway

>  And isn't it brittle
> to copy /usr/local/bin/python2.6?  A change to the location or version will
> break all these tests.

Done.
Changed to using 'which python'

http://codereview.chromium.org/6410134/diff/11001/chrome/test/chromeos/autote...
chrome/test/chromeos/autotest/files/client/site_tests/desktopui_PyAutoFunctionalTests/desktopui_PyAutoFunctionalTests.py:43:
utils.system(login_cmd)
On 2011/02/22 15:58:41, Chris Masone wrote:
> seems like pretty much all the above should be in initialize()

Done.

http://codereview.chromium.org/6410134/diff/11001/chrome/test/pyautolib/chrom...
File chrome/test/pyautolib/chromeos/enable_testing.py (right):

http://codereview.chromium.org/6410134/diff/11001/chrome/test/pyautolib/chrom...
chrome/test/pyautolib/chromeos/enable_testing.py:37: '', '--extra-chrome-flags',
action='append', default=[],
On 2011/02/22 15:58:41, Chris Masone wrote:
> What are these flags expected to be?  Adding and removing command line flags
> isn't really supported on chrome os, except by about:flags.

It's passed from pyauto.py. These are:
 '--homepage=about:blank',
 '--allow-file-access',
 '--enable-file-cookies',
 '--dom-automation',

These are the same set of flags used in chrome tests on desktops, to facilitate
several testing tasks.
--homepage=about:blank is just for speed.

[Chris Masone, 2011-02-22 22:53:54]

LGTM, then, but zel should still look at this.

[Nirnimesh, 2011-02-23 01:45:50]

+oshima, as Zel suggested.

[zel, 2011-02-23 19:40:22]

LGTM

...sorry for the delay

[oshima, 2011-02-24 20:37:19]

Do you still need my review?

- oshima

On Tue, Feb 22, 2011 at 5:45 PM, <nirnimesh@chromium.org> wrote:

> +oshima, as Zel suggested.
>
> http://codereview.chromium.org/6410134/
>

[Nirnimesh, 2011-02-24 20:39:59]

On 2011/02/24 20:37:19, oshima wrote:
> Do you still need my review?

Zel got to it. Thanks