Is it possible to write a Compose UI test that creates some composable UI, then removes it, and asse...

# compose

[Zach Klippenstein (he/him) [MOD]]

Is it possible to write a Compose UI test that creates some composable UI, then removes it, and assert that the Composable UI isn’t there using the AndroidComposeTestRule assertions? Example in thread.

[Zach Klippenstein (he/him) [MOD]]

For example:

val composeRule = createAndroidComposeTestRule(…)

@Test fun compositionDisappears() {
  // Adds a ComposeView to the view tree.
  setupComposeUi()

  composeRule.onNodeWithText("expected text").assertIsDisplayed()

  // Removes the ComposeView from the view tree entirely.
  tearDownComposeUi()

  // This line fails on alpha11 because no Compose views are found.
  composeRule.onNodeWithText("expected text").assertDoesNotExist()
}

[Zach Klippenstein (he/him) [MOD]]

This seems like a reasonable test to write to me. I would like to not have to check Espresso.onView(isInstanceOf(ComposeView::class.java)).check(exists()) or whatever manually, since the fact that the view is torn down by removing the Compose view entirely vs just composing empty content is an implementation detail.

[Zach Klippenstein (he/him) [MOD]]

Am I missing some test API somewhere? If not, I have a bug ready to file.

[Zach Klippenstein (he/him) [MOD]]

Filed a bug anyway: https://issuetracker.google.com/issues/179455327