Testing screens that uses DestinationsNavigator and Parcelable args about compose-destinations HOT 4 CLOSED

Hi @asrieltiago ! 👋

Thanks for reporting.
So yeah, this is something I haven't had time to fiddle with, unfortunately.
The one thing I can think of is that you can create a DestinationsNavigator like this:

     val navController = TestNavHostController(ApplicationProvider.getApplicationContext())

     fun destinationsNavigator(navBackStackEntry: NavBackStackEntry): DestinationsNavigator {
         return DestinationsNavController(navController, navBackStackEntry)
     }
    
    //...
        DestinationsNavHost(navGraph = NavGraphs.root, navController = navController)

I'm not sure if this helps or not. I'd have to fully understand what you're trying to do, so I can test on my side.
Is this an open-source project I can take a look at?
From my understanding, you want to test after navigating if the Parcelable args are correct on the other side?

from compose-destinations.

Or you can create an implementation of DestinationsNavigator any way you want since it is an interface. Again.. not sure if this helps 😅

from compose-destinations.

I made the UI test work, following your idea of creating a class inheriting from the DestinationsNavigator interface.

In the end it was something simple, thanks for the quick answer and maybe this will help the next ones who are going to test the UI.

from compose-destinations.

If you need an empty implementation of DestinationsNavigator, the library has an EmptyDestinationsNavigator 😅
I thought you wanted to test navigating specifically! Yeah if all you need to test is screens on their own, then this will work for you!

from compose-destinations.