Drop dependency to Chromium in WebRtcJniBootTest.

webrtc/sdk/android/instrumentationtests/src/org/webrtc/WebRtcJniBootTest.java

Index: webrtc/sdk/android/instrumentationtests/src/org/webrtc/WebRtcJniBootTest.java
diff --git a/webrtc/sdk/android/instrumentationtests/src/org/webrtc/WebRtcJniBootTest.java b/webrtc/sdk/android/instrumentationtests/src/org/webrtc/WebRtcJniBootTest.java
index c3b5b45798a4129dfdf020d94f41c11c2a505f8d..adc4e1ebd53c19059a4b8ae1a6f50f39e5dc786e 100644
--- a/webrtc/sdk/android/instrumentationtests/src/org/webrtc/WebRtcJniBootTest.java
+++ b/webrtc/sdk/android/instrumentationtests/src/org/webrtc/WebRtcJniBootTest.java
@@ -12,7 +12,7 @@ package org.appspot.apprtc.test;
 
 import android.support.test.InstrumentationRegistry;
 import android.support.test.filters.SmallTest;
-import org.chromium.base.test.BaseJUnit4ClassRunner;
+import android.support.test.runner.AndroidJUnit4;
 import org.junit.Test;
 import org.junit.runner.RunWith;
 import org.webrtc.PeerConnectionFactory;
@@ -20,7 +20,7 @@ import org.webrtc.PeerConnectionFactory;
 // This test is intended to run on ARM and catch LoadLibrary errors when we load the WebRTC
 // JNI. It can't really be setting up calls since ARM emulators are too slow, but instantiating
 // a peer connection isn't timing-sensitive, so we can at least do that.
-@RunWith(BaseJUnit4ClassRunner.class)
+@RunWith(AndroidJUnit4.class)
 public class WebRtcJniBootTest {
   @Test
   @SmallTest