tutorials/Android-Tutorial-Test-ShowCase
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Issue#39 Added workaround for slow SplashActivity tests.

Browse source 
Referenced the issues 676 reported on Android-Test. aka seems to be an issue with finishing activity and ActivityScenario.moteToState(DESTROYED).
This commit is contained in:
Gergely Hegedus 2022-01-26 01:31:01 +02:00
parent 96e2f492c9
commit a9a2858242
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
app/src/sharedTest/java/org/fnives/test/showcase/ui/splash/SplashActivityTest.kt
View file

@ -67,6 +67,8 @@ class SplashActivityTest : KoinTest {
splashRobot.assertHomeIsStarted()
.assertAuthIsNotStarted()
workaroundForActivityScenarioCLoseLockingUp()
}
/** GIVEN loggedOffState WHEN opened after some time THEN AuthActivity is started */
@ -80,6 +82,8 @@ class SplashActivityTest : KoinTest {
splashRobot.assertAuthIsStarted()
.assertHomeIsNotStarted()
workaroundForActivityScenarioCLoseLockingUp()
}
/** GIVEN loggedOffState and not enough time WHEN opened THEN no activity is started */
@ -108,4 +112,17 @@ class SplashActivityTest : KoinTest {
splashRobot.assertHomeIsNotStarted()
.assertAuthIsNotStarted()
}
/**
* This should not be needed, we shouldn't use sleep ever.
* However, it seems to be and issue described here: https://github.com/android/android-test/issues/676
*
* If an activity is finished in code, the ActivityScenario.close() can hang 30 to 45 seconds.
* This sleeps let's the Activity finish it state change and unlocks the ActivityScenario.
*
* As soon as that issue is closed, this should be removed as well.
*/
private fun workaroundForActivityScenarioCLoseLockingUp() {
Thread.sleep(1000L)
}
}