CTS: Fixed NotificationTest for watches, since they always suppress
notifications
NotificationTest.java asserts that there are 0 suppressed notifications
by default, but watches always suppress notifications intentionally so
they can manage their own notifications. Tweaked the test to exclude
this assertion for watches.
Bug: 64606626
Test:
cts-tf > run cts -m CtsIncidentHostTestCases -t
com.android.server.cts.NotificationTest#testZenMode -l DEBUG -s
01f2301c0f6ac226 -a armeabi-v7a
08-17 13:16:50 I/ResultReporter: Invocation finished in 3m 8s. PASSED:
1, FAILED: 0, MODULES: 1 of 1
Change-Id: Ib553d9ba83e6f8371c02f34451afb2901b0a2b6f
(cherry picked from commit 5abd011195fd2bcc4adeed5c62e5d2525ad79021)
diff --git a/hostsidetests/incident/src/com/android/server/cts/NotificationTest.java b/hostsidetests/incident/src/com/android/server/cts/NotificationTest.java
index 10a1b77..f91c8a7 100644
--- a/hostsidetests/incident/src/com/android/server/cts/NotificationTest.java
+++ b/hostsidetests/incident/src/com/android/server/cts/NotificationTest.java
@@ -29,6 +29,9 @@
* cts-tradefed run singleCommand cts-dev -d --module CtsIncidentHostTestCases
*/
public class NotificationTest extends ProtoDumpTestCase {
+ // These constants are those in PackageManager.
+ public static final String FEATURE_WATCH = "android.hardware.type.watch";
+
/**
* Tests that at least one notification is posted, and verify its properties are plausible.
*/
@@ -67,9 +70,13 @@
assertEquals(ZenMode.ZEN_MODE_OFF, zenProto.getZenMode());
assertEquals(0, zenProto.getEnabledActiveConditionsCount());
- assertEquals(0, zenProto.getSuppressedEffects());
- assertEquals(0, zenProto.getSuppressorsCount());
+
+ // b/64606626 Watches intentionally suppress notifications always
+ if (!getDevice().hasFeature(FEATURE_WATCH)) {
+ assertEquals(0, zenProto.getSuppressedEffects());
+ assertEquals(0, zenProto.getSuppressorsCount());
+ }
+
zenProto.getPolicy();
}
}
-
