[AWARE] Validate that forbidden callbacks aren't triggered
The test code already checks for unexpected callbacks - but that
only be checked at the app level. I.e. callbacks which were not
masked out by the framework. Add code which checks the actual HAL
callback count to verify that unexpected (forbidden) callbacks
aren't triggered.
Rationale: even if they don't reach the app they still indicate
that the HAL woke-up the host to deliver unwanted callbacks. This
can result in power increase.
Bug: 31940045
Test: Discovery tests (continue to) pass
Change-Id: I159d533bb15c790e911b6385fa3b3802fe949d22
diff --git a/acts/tests/google/wifi/aware/functional/DiscoveryTest.py b/acts/tests/google/wifi/aware/functional/DiscoveryTest.py
index 76af4a2..a1ace3e 100644
--- a/acts/tests/google/wifi/aware/functional/DiscoveryTest.py
+++ b/acts/tests/google/wifi/aware/functional/DiscoveryTest.py
@@ -277,6 +277,9 @@
autils.verify_no_more_events(p_dut, timeout=0)
autils.verify_no_more_events(s_dut, timeout=0)
+ # verify that forbidden callbacks aren't called
+ autils.validate_forbidden_callbacks(p_dut, {aconsts.CB_EV_MATCH: 0})
+
def verify_discovery_session_term(self, dut, disc_id, config, is_publish,
term_ind_on):
"""Utility to verify that the specified discovery session has terminated (by
@@ -433,6 +436,13 @@
# verify that there were no other events
autils.verify_no_more_events(dut)
+ # verify that forbidden callbacks aren't called
+ if not term_ind_on:
+ autils.validate_forbidden_callbacks(dut, {
+ aconsts.CB_EV_PUBLISH_TERMINATED: 0,
+ aconsts.CB_EV_SUBSCRIBE_TERMINATED: 0
+ })
+
def discovery_mismatch_test_utility(self,
is_expected_to_pass,
p_type,