🍈 Unify application context usage.

android_webview/javatests/src/org/chromium/android_webview/test/CookieManagerStartupTest.java

Index: android_webview/javatests/src/org/chromium/android_webview/test/CookieManagerStartupTest.java
diff --git a/android_webview/javatests/src/org/chromium/android_webview/test/CookieManagerStartupTest.java b/android_webview/javatests/src/org/chromium/android_webview/test/CookieManagerStartupTest.java
index 65051028cb3e980278ee13c1eca6ce1460189829..d281f8614512c3099cbc2624fbac66ea2b271ba3 100644
--- a/android_webview/javatests/src/org/chromium/android_webview/test/CookieManagerStartupTest.java
+++ b/android_webview/javatests/src/org/chromium/android_webview/test/CookieManagerStartupTest.java
@@ -30,8 +30,10 @@ public class CookieManagerStartupTest extends AwTestBase {
     @Override
     protected void setUp() throws Exception {
         super.setUp();
-        ContextUtils.initApplicationContext(getActivity().getApplicationContext());
-    }
+        Context appContext = getInstrumentation().getTargetContext().getApplicationContext();
+        ContextUtils.initApplicationContext(appContext);

[Yaron, 2016/04/25 14:09:45]

I'm not familiar enough with aw setup but possibly something to move to
AwTestBase?

[Peter Wen, 2016/04/25 15:30:30]

Move the context stuff to AwTestBase, though I believe other than CookieManager,
the rest load native through AwTestRunnerActivity.onCreate, which already sets
ContextUtils.

Added comment to distinguish why CookieManager needs its own loadLibrary and not
AwTestRunnerActivity's in onCreate.

+        AwBrowserProcess.loadLibrary(appContext);
+    };
 
     @Override
     protected boolean needsBrowserProcessStarted() {