commit 843b3482cc6eaa26f8af8184a1da5e28c9e02f1d
author kwaky <kwaky@google.com> Thu Apr 30 15:47:00 2020 -0700
committer kwaky <kwaky@google.com> Thu May 07 16:22:11 2020 -0700
tree 32f39267529ec7ba6dc024ba03ec262ee3909933
parent 289c104c13bb8d6682d05ffdd9b01c45f97589cd

Refactor testDisableKeyguard_thenSettingCredential_reenablesKeyguard
test to check Device secured/locked status after setting credentials
instead of checking for the visibility of Keyguard.

testDisableKeyguard_thenSettingCredential_reenablesKeyguard was flaky
when we were checking for the keyguard visibility status after setting
credentials. Checking for the secured/locked status is both reliable and
valid (the test fails if we don't set credentials.)

Bug: 154829257
Test: atest CtsWindowManagerDeviceTestCases:KeyguardLockedTests
Change-Id: I085b12081497f1e8d2322c94ed9999af63f70d17