Skip test that uses DeviceConfig.
Following on from Ic7b68809c9e2001582d10bb183e351d6572a2bbb there is no
reliable way to detect if the device actually is or isn't using
DeviceConfig flag to control Safety Center. We assume always that it
isn't, but in this test that assumption (if it is not true) causes an
error where we turn Safety Center off and then leave it stuck off.
Test: atest CtsSafetyCenterTestCases
Bug: 423822838
Change-Id: Id6da9f2d0ce934a4e1bde349d8cbb4e4ad151d92
diff --git a/tests/cts/safetycenter/src/android/safetycenter/cts/SafetyCenterManagerTest.kt b/tests/cts/safetycenter/src/android/safetycenter/cts/SafetyCenterManagerTest.kt
index 697df48..d6481bf 100644
--- a/tests/cts/safetycenter/src/android/safetycenter/cts/SafetyCenterManagerTest.kt
+++ b/tests/cts/safetycenter/src/android/safetycenter/cts/SafetyCenterManagerTest.kt
@@ -97,6 +97,7 @@
import kotlinx.coroutines.TimeoutCancellationException
import org.junit.Assume.assumeFalse
import org.junit.Assume.assumeTrue
+import org.junit.Ignore
import org.junit.Rule
import org.junit.Test
import org.junit.runner.RunWith
@@ -887,6 +888,9 @@
}
}
+ // We can't know if DeviceConfig is in use or not, so this test is ignored.
+ // See b/423822838 for more details.
+ @Ignore
@Test
fun safetyCenterEnabledChanged_whenNoDeviceConfigFlag_receiverNotCalled() {
assumeFalse(
