Hey hey, any super duper compose testers out that could answer a couple questions for me? :) I want...

# compose

[Nathan Castlehow]

Hey hey, any super duper compose testers out that could answer a couple questions for me? :)

I want to do a quick smoke test where I open particular routes in the app. Similar to jetsnack https://github.com/android/compose-samples/blob/5f250deb3534a6488e45c72b1d101665c5ba0de4/Jetsnack/app/src/androidTest/java/com/example/jetsnack/AppTest.kt

Qns in thread

[Nathan Castlehow]

1) Do we have to set content or can we let the activity just run its course?

[Nathan Castlehow]

2) I have a current test class where i don’t call set content and let activity run its course. It has two test cases which are identical. The first one always fails due to a specific node not being present and then the second one works. Assuming we don’t have to explicitly call setcontent is there a waitUntil a node is present type deal? I see we have a waitUntil function but can’t find a way to check for a particular node without doing a full assert.

[Nathan Castlehow]

Granted a more granular approach to test screen behaviour by calling set content would also be valuable however for a first past just want a very coarse integration type test.

[Nathan Castlehow]

For anyone reading this later on the missing piece was registering a custom idling resource. Set this up so each screen would mark when its idle / not. Similar exists in espresso.