Update instrumentation tests to use PreTestHooks for policies

chrome/test/android/javatests/src/org/chromium/chrome/test/ChromeInstrumentationTestRunner.java

Index: chrome/test/android/javatests/src/org/chromium/chrome/test/ChromeInstrumentationTestRunner.java
diff --git a/chrome/test/android/javatests/src/org/chromium/chrome/test/ChromeInstrumentationTestRunner.java b/chrome/test/android/javatests/src/org/chromium/chrome/test/ChromeInstrumentationTestRunner.java
index 16cfa52eb617d161d75c280cfac7c71aaed4cab4..2abc1717fbf47f2923d4722ff42eb589fc695a90 100644
--- a/chrome/test/android/javatests/src/org/chromium/chrome/test/ChromeInstrumentationTestRunner.java
+++ b/chrome/test/android/javatests/src/org/chromium/chrome/test/ChromeInstrumentationTestRunner.java
@@ -19,6 +19,7 @@
 import org.chromium.chrome.browser.util.FeatureUtilities;
 import org.chromium.chrome.test.util.DisableInTabbedMode;
 import org.chromium.net.test.BaseHttpTestServer;
+import org.chromium.policy.test.annotations.Policies;
 import org.chromium.ui.base.DeviceFormFactor;
 
 import java.io.File;
@@ -214,6 +215,8 @@ protected void addTestHooks(BaseTestResult result) {
         super.addTestHooks(result);
         result.addSkipCheck(new DisableInTabbedModeSkipCheck());
         result.addSkipCheck(new ChromeRestrictionSkipCheck());
+
+        result.addPreTestHook(Policies.getRegistrationHook());

[Yaron, 2015/10/16 17:51:52]

Do all chrome tests need these policies set up? Could you restrict it to a
policy test suite base class for classes which depend on it?

Also, the CL description only talks about webview (hence my confusion :)

[dgn, 2015/10/20 10:09:46]

We want to set the cached policies before the application set up, so doing it
before the test case is initialized makes sure we do it early enough.
Updated the description

     }
 
     private class ChromeRestrictionSkipCheck extends RestrictionSkipCheck {