I’m running a really simple UI Unit test that tests a very basic composable and running it on fireba...

# compose

[chatterInDaSkull]

I’m running a really simple UI Unit test that tests a very basic composable and running it on firebase testlab but leading to Test instrumentation process crashed.

Running it on Compose version 1.3 and Low-resolution MDPI phone, Virtual, API Level 28

Has anyone come across this?
More details in thread🧵

[chatterInDaSkull]

Crash logs of the test

firebase test lab crash logs.txt

[chatterInDaSkull]

Simple test code

Untitled.cpp

[chatterInDaSkull]

I couldn’t find anything on issue tracker

[czuckie]

I really don't want to hit you with a 😶 , but it really isn't kotlin specific.

Have you tried running your tests with the test orchestrator locally? Have you mimic'd the device configuration as closely as possible? Why do you think compose has anything to do with it?

There is nothing in the log beyond the com.r.test.util.android.runner.RhAndroidJUnitTestRunner which stands out as fishy though. I'd check that runner to see if you can put in any logging so you can see at what point your tests are dying, because it doesn't look like you're getting to even executing it, if it really is just called SomeComposableTest.

Also, don't prefix your test names with test, the @Test annotation is good enough I promise 😄

[chatterInDaSkull]

I really don’t want to hit you with a 😶 , but it really isn’t kotlin specific.

ah my intention of bringing up here is because its #compose

Have you tried running your tests with the test orchestrator locally? Have you mimic’d the device configuration as closely as possible? Why do you think compose has anything to do with it?

works locally. Works with the same snapshot of the device thats on the test labl when running locally. It works when I remove all compose references in the test 🙂 basically becomes an empty test.

There is nothing in the log beyond the com.r.test.util.android.runner.RhAndroidJUnitTestRunner which stands out as fishy though.

Correct. Its almost like the test never starts. I’ll try adding in the logging

Also, don’t prefix your test names with test, the @Test annotation is good enough I promise 😄

🙏 sounds good

[chatterInDaSkull]

Also happy to delete the post if you think there’s a better channel for it

[czuckie]

the kotlin workspace is specifically for kotlin topics, so although you're using the compose framework, the issue you're facing isn't strictly tied to compose, them's the rules, but I'm not an enforcer, just trying to help out if I can.

Unfortunately, to my knowledge there is no better place for this kind of conversation.

[czuckie]

Good luck though!

[chatterInDaSkull]

Dug around a little bit more to find a deeper problem

SIGSEV.txt