[Compose] Optimize to test "SharedFlow" execution in Composable with Robolectric

[luongvo]

Why

According to the last implementation of running the Jetpack Compose UI Test with Robolectric, we have to switch the error from SharedFlow to StateFlow because we can not make it to be testable with Robolectric.

Using LaunchedEffect in Jetpack Compose is a standard best practice, and it's hard to find a replacement for LaunchedEffect. So in the big picture, if we can not test SharedFlow execution by LaunchedEffect in Composable with Robolectric, we cannot use Robolectric as our main testing framework for Jetpack Compose to cover all project business logic.

Hence, we should research & find a valid way to test SharedFlow execution in Composable with Robolectric without converting it to StateFlow. This also helps to apply using viewModel.error.collectAsEffect for error handling instead of

android-templates/sample-compose/app/src/main/java/co/nimblehq/sample/compose/ui/screens/home/HomeScreen.kt

Lines 38 to 39 in b9304c7

	val error: Throwable? by viewModel.error.collectAsStateWithLifecycle()
	error?.showToast(context)

Who Benefits?

Developers

[ryan-conway]

@luongvo This issue seems very opened ended, I can't see how to define clear acceptance criteria here 🤔 Do you have a concrete suggestion for how to resolve this issue?

[luongvo]

@luongvo This issue seems very opened ended, I can't see how to define clear acceptance criteria here 🤔 Do you have a concrete suggestion for how to resolve this issue?

@ryan-conway It's still an experiment. However, I found a way to resolve it, so clarifying it in the PR is better 🙏