Use Sync FakeServer in Android tests via custom APK

chrome/android/javatests/src/org/chromium/chrome/browser/sync/SyncTest.java

Index: chrome/android/javatests/src/org/chromium/chrome/browser/sync/SyncTest.java
diff --git a/chrome/android/javatests/src/org/chromium/chrome/browser/sync/SyncTest.java b/chrome/android/javatests/src/org/chromium/chrome/browser/sync/SyncTest.java
index 768d33fda0a54f076290bdb3a1d4a6d0579a6156..02dddf9508e32262318fc57a1df339c312fd6e02 100644
--- a/chrome/android/javatests/src/org/chromium/chrome/browser/sync/SyncTest.java
+++ b/chrome/android/javatests/src/org/chromium/chrome/browser/sync/SyncTest.java
@@ -6,10 +6,11 @@ package org.chromium.chrome.browser.sync;
 
 import android.accounts.Account;
 import android.app.Activity;
+import android.test.suitebuilder.annotation.LargeTest;
 import android.util.Log;
 
 import org.chromium.base.ThreadUtils;
-import org.chromium.base.test.util.HostDrivenTest;
+import org.chromium.base.test.util.Feature;
 import org.chromium.chrome.browser.identity.UniqueIdentificationGenerator;
 import org.chromium.chrome.browser.identity.UniqueIdentificationGeneratorFactory;
 import org.chromium.chrome.browser.identity.UuidBasedUniqueIdentificationGenerator;
@@ -65,10 +66,25 @@ public class SyncTest extends ChromeShellTestBase {
                 mSyncController = SyncController.get(mContext);
             }
         });
-        SyncTestUtil.verifySyncServerIsRunning();
+        SyncTestUtil.useFakeServer(getInstrumentation().getTargetContext());
     }
 
-    @HostDrivenTest
+    @Override
+    protected void tearDown() throws Exception {
+        ThreadUtils.runOnUiThreadBlocking(new Runnable() {

[rlarocque, 2014/08/09 01:19:59]

tearDown() is not called on the UI thread?  What thread do these unit tests run
on?  Is it safe for this thread to block during sync shutdown?

[Yaron, 2014/08/12 17:22:03]

These are called on a separate test thread (android tests by default run on this
thread unless you annotate the test with @UIThreadTest).

+            @Override
+            public void run() {
+                mSyncController.stop();
+                SyncTestUtil.deleteFakeServer();
+            }
+        });
+
+        super.tearDown();
+    }
+
+
+    @LargeTest
+    @Feature({"Sync"})
     public void testGetAboutSyncInfoYieldsValidData() throws Throwable {
         setupTestAccountAndSignInToSync(FOREIGN_SESSION_TEST_MACHINE_ID);
 
@@ -86,7 +102,8 @@ public class SyncTest extends ChromeShellTestBase {
         assertTrue("Couldn't get about info.", gotInfo);
     }
 
-    @HostDrivenTest
+    @LargeTest
+    @Feature({"Sync"})
     public void testAboutSyncPageDisplaysCurrentSyncStatus() throws InterruptedException {
         setupTestAccountAndSignInToSync(FOREIGN_SESSION_TEST_MACHINE_ID);
 
@@ -130,7 +147,8 @@ public class SyncTest extends ChromeShellTestBase {
                 hadExpectedStatus);
     }
 
-    @HostDrivenTest
+    @LargeTest
+    @Feature({"Sync"})
     public void testDisableAndEnableSync() throws InterruptedException {
         setupTestAccountAndSignInToSync(FOREIGN_SESSION_TEST_MACHINE_ID);
         Account account =
@@ -146,6 +164,14 @@ public class SyncTest extends ChromeShellTestBase {
         SyncTestUtil.verifySignedInWithAccount(mContext, account);
     }
 
+    @LargeTest
+    @Feature({"Sync"})
+    public void testFakeServer() throws Exception {
+        // This test simply ensures the functionality of signing in and using FakeServer. It is
+        // unncessary once we have other enabled tests.
+        setupTestAccountAndSignInToSync(FOREIGN_SESSION_TEST_MACHINE_ID);
+    }
+
     private void setupTestAccountAndSignInToSync(
             final String syncClientIdentifier)
             throws InterruptedException {