Do I have to do something special to run tests in compose? I wrote this simple test on androidTest f...

# compose

[nglauber]

Do I have to do something special to run tests in compose?
I wrote this simple test on androidTest folder:

@RunWith(JUnit4::class)
class ExampleInstrumentedTest {
    @get:Rule
    val composeTestRule = createComposeRule()

    @Test
    fun testProductQuantity() {
        var quantity = 0

        composeTestRule.setContent {
            MaterialTheme {
                MyComponent(onUpdate = { quantity += it })
            }
        }
        findByTag("Product_Inc")
            .doClick()
            .doClick()

        runOnIdleCompose {
            assertEquals(quantity, 2)
        }
    }
}

When I press the run button, I can see the loading on the Run panel on Android Studio, but after a few seconds I get this message:

java.lang.AssertionError: Activity never becomes requested state "[CREATED, STARTED, RESUMED, DESTROYED]" (last lifecycle transition = "PRE_ON_CREATE")

[henrikhorbovyi]

Could you share you MyComponent implementation?

[henrikhorbovyi]

I tried here and is everything fine.

@Composable
fun MyComponent(onUpdate: (Int) -> Unit) {
    val (value, onChanged) = state { 0 }
    Button(
        modifier = Modifier.testTag("component_tag"),
        text = { Text("Clicke me") },
        onClick = {
            onChanged(value + 1)
            onUpdate(value)
        })
}

[nglauber]

thanks @henrikhorbovyi. I don’t think it matters… I tried your code and get the same error… 😩

[henrikhorbovyi]

Do you think is it a lib error and not about the implementation?

[nglauber]

not sure… which compose version you’re using? I’m on dev14

[henrikhorbovyi]

Same here

[henrikhorbovyi]

If you comment the assert the test still breaks?

runOnIdleCompose {
    assertEquals(2, quantity)
}

[henrikhorbovyi]

So we can check if the problem is there

[Adam Powell]

This might be a silly question, but is your test device or emulator screen off/screen locked?

[nglauber]

@Adam Powell I’m using emulator API 29. And no, the screen is not locked

[Adam Powell]

had to ask just in case 🙂

[nglauber]

For future reference:
I needed to add this on AndroidManifest.xml

<activity android:name="androidx.activity.ComponentActivity" />