network_WiFi_FastReconnectInDarkResume: fix test logic
The test should measure the difference in dark resume count instead of
looking directly at the dark resume number.
BUG=chrome-os-partner:43894
TEST=`test_that --fast -b oak dut network_WiFi_FastReconnectInDarkResume
--iterations 3`
Change-Id: If7433be6affa54e0c7aea358f6dfe6b57d2dffe2
Reviewed-on: https://chromium-review.googlesource.com/319957
Commit-Ready: Wei-Ning Huang <wnhuang@chromium.org>
Tested-by: Wei-Ning Huang <wnhuang@chromium.org>
Reviewed-by: Samuel Tan <samueltan@chromium.org>
diff --git a/server/site_tests/network_WiFi_FastReconnectInDarkResume/network_WiFi_FastReconnectInDarkResume.py b/server/site_tests/network_WiFi_FastReconnectInDarkResume/network_WiFi_FastReconnectInDarkResume.py
index 7367c85..fdf4185 100644
--- a/server/site_tests/network_WiFi_FastReconnectInDarkResume/network_WiFi_FastReconnectInDarkResume.py
+++ b/server/site_tests/network_WiFi_FastReconnectInDarkResume/network_WiFi_FastReconnectInDarkResume.py
@@ -29,6 +29,7 @@
# Enable the dark connect feature in shill.
with client.wake_on_wifi_features(wifi_client.WAKE_ON_WIFI_DARKCONNECT):
logging.info('Set up WoWLAN')
+ prev_dark_resume_count = self.dr_utils.count_dark_resumes()
with self.dr_utils.suspend():
# Wait for suspend actions to finish.
@@ -45,7 +46,9 @@
wifi_client.DARK_RESUME_WAIT_TIME_SECONDS)
client.check_connected_on_last_resume()
- if self.dr_utils.count_dark_resumes() != 1:
+ dark_resume_count = (self.dr_utils.count_dark_resumes() -
+ prev_dark_resume_count)
+ if dark_resume_count != 1:
# If there was more than 1 dark resume, the DUT might not have
# reconnected on the dark resume triggered by the disconnect.
raise error.TestFail('Expected exactly one dark resume')
