Is it possible to test Compose without running the test on a device/emulator?

it should work fine with robolectric, we have a few robolectric tests lurking around in compose itself

If you have any of those Robolectric tests from within compose handy could you link them? I was trying to write some in Robolectric but I kept getting:

java.lang.IllegalStateException: Functions that involve synchronization (Assertions, Actions, Synchronization; e.g. assertIsSelected(), doClick(), runOnIdle()) cannot be run from the main thread. Did you nest such a function inside runOnIdle {}, runOnUiThread {} or setContent {}?

looks like there are definitely some workarounds floating about in these: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:compose/ui/ui/src/test/kotlin/androidx/compose/ui/test/ComposeUiRobolectricTestRunner.kt;l=37

@Adam Powell I thought each composable would be able to be tested on the jvm. Maybe I misinterpreted something from months ago. I don't think it's the worst thing if I need to test my composables on device. Anything that gets me away from robolectric because that always ends up being a dumpster fire.

If you write a composable function like

ContextAmbient.current.getSystemService(...)...

then that's a platform-specific composable 🙂

@David Albers did you get robolectric tests up and running?

Hey @Mini, I was able to test Composables if I used this runner or upgraded to Robolectric 4.4. However, there are some view-testing function such as

assertIsDisplayed()

(this) that I never figured out how to get working in Robolectric.

Did you create your own copy of the runner?

Hi Allan. Right, I copied the

ComposeUiRobolectricTestRunner

into my project. Then I set it as the runner for Robolectric tests like so:

@RunWith(ComposeUiRobolectricTestRunner::class)
class YourComposableTest {
....

hope that helps!