Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[flexiglass] Fixes failing test after coroutine lib upgrade.

Browse Source 
The changed test case started failing after the coroutines library has
been upgraded; not sure why.

This fixes it by toggling the isUnlocked state to trigger the flow under
test to update (since updating getAuthenticationMethod() or
isLockscreenEnabled does not trigger this flow to update).

Bug: 292807808
Test: N/A
Change-Id: Ie26c407931e52a98235c575adf9ba12186caa3a2
Merged-In: Ie26c407931e52a98235c575adf9ba12186caa3a2
(cherry picked from commit cd26767566)
This commit is contained in:
Alejandro Nijamkin
2023-07-25 15:08:50 -07:00
committed by Colin Cross
parent a9dafc3734
commit 0636ffb746
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
packages/SystemUI/tests/src/com/android/systemui/authentication/domain/interactor/AuthenticationInteractorTest.kt
View File

@@ -86,6 +86,22 @@ class AuthenticationInteractorTest : SysuiTestCase() {
underTest.biometricUnlock()
runCurrent()
// Toggle isUnlocked, twice.
//
// This is done because the underTest.isUnlocked flow doesn't receive values from
// just changing the state above; the actual isUnlocked state needs to change to
// cause the logic under test to "pick up" the current state again.
//
// It is done twice to make sure that we don't actually change the isUnlocked
// state from what it originally was.
utils.authenticationRepository().setUnlocked(
!utils.authenticationRepository().isUnlocked.value
)
runCurrent()
utils.authenticationRepository().setUnlocked(
!utils.authenticationRepository().isUnlocked.value
)
runCurrent()
assertThat(isUnlocked).isTrue()
}