Hey hey, Testing question if anyone has a quick se...
# compose
n
Hey hey, Testing question if anyone has a quick sec -> “Compose tests are synchronized by default with your UI. When you call an assertion or an action via the
ComposeTestRule
, the test will be synchronized beforehand, waiting until the UI tree is idle” Does this synchronisation on assertions include custom idling resources which have been registered? Or would I have to call waitForIdle() in between each line that makes async changes (eg. a network call)?
To anyone that reads this later it feels like registering it is enough. We were trying to chase down some flaky tests and weren’t sure if this was contributing to it.