Fix CTS test to not rely on assumptions / side-effects
Pass a valid IntentFilter to addPreferredActivity() so that the
permission test under examination isn't muddied by invalid-argument
considerations.
Bug 11543966
Change-Id: I7c169cf64109ce44ada839a99627ff35a18cb735
diff --git a/tests/tests/permission/src/android/permission/cts/PackageManagerRequiringPermissionsTest.java b/tests/tests/permission/src/android/permission/cts/PackageManagerRequiringPermissionsTest.java
index 7ff67eb..6f4c11a 100644
--- a/tests/tests/permission/src/android/permission/cts/PackageManagerRequiringPermissionsTest.java
+++ b/tests/tests/permission/src/android/permission/cts/PackageManagerRequiringPermissionsTest.java
@@ -16,6 +16,8 @@
package android.permission.cts;
+import android.content.Intent;
+import android.content.IntentFilter;
import android.content.pm.PackageManager;
import android.test.AndroidTestCase;
import android.test.suitebuilder.annotation.SmallTest;
@@ -59,7 +61,9 @@
*/
public void testAddPreferredActivity() {
try {
- mPackageManager.addPreferredActivity(null, 0, null, null);
+ IntentFilter filter = new IntentFilter(Intent.ACTION_MAIN);
+ filter.addCategory(Intent.CATEGORY_HOME);
+ mPackageManager.addPreferredActivity(filter, 0, null, null);
fail("PackageManager.addPreferredActivity did not throw" +
" SecurityException as expected");
} catch (SecurityException e) {
