Remove Context from mockContentResolver to avoid a Null Pointer Exception

mockContentResolver was updated to call a function on the context provided
in its constructor which caused an exception with mockContext. Instead leaving
the context out of the constructor skips this function call and doesn't affect
the test.

Test: Run unit tests with "runtest bluetooth"
Change-Id: I7a597c5864943d3d53dcb551bf3d3bafb4beb5ed

diff --git a/tests/src/com/android/bluetooth/map/BluetoothMapContentObserverTest.java b/tests/src/com/android/bluetooth/map/BluetoothMapContentObserverTest.java
index 01f752f..4b185ee 100644 (file)
--- a/tests/src/com/android/bluetooth/map/BluetoothMapContentObserverTest.java
+++ b/tests/src/com/android/bluetooth/map/BluetoothMapContentObserverTest.java
@@ -38,7 +38,7 @@ public class BluetoothMapContentObserverTest extends AndroidTestCase {
         if (Looper.myLooper() == null) Looper.prepare();
 
         Context mockContext = mock(Context.class);
-        MockContentResolver mockResolver = new MockContentResolver(mockContext);
+        MockContentResolver mockResolver = new MockContentResolver();
         ExceptionTestProvider mockProvider = new ExceptionTestProvider(mockContext);
         mockResolver.addProvider("sms", mockProvider);