Initial checkin of the me2me pyauto automation:

chrome/test/functional/PYAUTO_TESTS

Index: chrome/test/functional/PYAUTO_TESTS
===================================================================
--- chrome/test/functional/PYAUTO_TESTS	(revision 140048)
+++ chrome/test/functional/PYAUTO_TESTS	(working copy)
@@ -40,7 +40,7 @@
       'bookmarks',
       'browser',
       'browsing_data',
-      'chromoting_basic',
+      'chromoting.it2me_basic',
       'codesign',
       'content',
       'cookies',
@@ -285,7 +285,7 @@
       # You cannot resize the browser window on ChromeOS.
       '-browser.BrowserTest.testWindowResize',
       # ChromeOS doesn't yet support the chromoting host.
-      '-chromoting_basic',
+      '-chromoting.it2me_basic',

[simonmorris, 2012/07/30 22:44:24]

Should this line be '-chromoting', to block all the chromoting tests? My guess
is that none of them will run if the chromoting host won't run.

[yihongg1, 2012/08/03 00:40:06]

We are only enabling chromoting.it2me_basic on continuous right now. This is to
disable that test on continuous and chromeos. We don't need to include others
because we didn't add those in the first place anyway.
On 2012/07/30 22:44:24, simonmorris wrote:

       # No codesign verification on ChromeOS.
       '-codesign',
       # Import tests are invalid on ChromeOS since Chrome is the only browser.
@@ -482,7 +482,7 @@
       # Permanently-disabled tests.
       # ===========================
       # The chromoting webapp isn't currently available when FULL is run.
-      '-chromoting_basic',
+      '-chromoting.it2me_basic',

[simonmorris, 2012/07/30 22:44:24]

Just '-chromoting'?

[yihongg1, 2012/08/03 00:40:06]

Same as above explanation.
On 2012/07/30 22:44:24, simonmorris wrote:

 
       # ==================================================
       # Disabled tests that need to be investigated/fixed.