Update CTS tests: remove acquireContentProviderClient test.
This test is dependent upon whether or not the content provider defines
any path permissions - if it does the acquireContentProvider call will
not throw. Since acquiring the content provider alone is no the important
part of the test, remove it. Querying/updating the content provider is
handled by the other test cases here, and these are what matter.
Change-Id: I880d01fe25b69c705bfb81d0c76a225e5100a981
Signed-off-by: Mathew Inwood <mathewi@google.com>
diff --git a/tests/tests/permission/src/android/permission/cts/ContactsProviderTest.java b/tests/tests/permission/src/android/permission/cts/ContactsProviderTest.java
index cd14094..51e54df 100644
--- a/tests/tests/permission/src/android/permission/cts/ContactsProviderTest.java
+++ b/tests/tests/permission/src/android/permission/cts/ContactsProviderTest.java
@@ -30,17 +30,6 @@
* Verify permissions are enforced.
*/
public class ContactsProviderTest extends AndroidTestCase {
- @SmallTest
- public void testAcquireContentProviderClient() throws Exception {
- try {
- final ContentProviderClient provider = getContext().getContentResolver().
- acquireContentProviderClient(Contacts.AUTHORITY);
- fail("acquireContentProviderClient(Contacts.AUTHORITY) did not throw"
- + " SecurityException as expected");
- } catch (SecurityException se) {
- // Expected Exception
- }
- }
/**
* Verifies that query(ContactsContract.Contacts.CONTENT_URI) requires
