IssueTracker

P.S. Actually we cannot running Instrumented Test when using NavigationUI.
When initialize the AppBarConfiguration, it will call the final method of NavGraph (findNode) and we cannot mock it.

I also ran into this today while trying to add a FragmentScenario test. Followed the testing documentation and arrived at the same place. AppBarConfiguration attempts to interact with NavGraph and crashes.

Yep, we should have a better testing story that doesn't depend on using mocks.

One and only solution is to use Mockito in Espresso tests. Which is actually is almost equal to no solution. We strictly do not use Mockito in our integrations tests running on devices because that is very fragile and causes huge amount of issues when using on different SDK versions. This makes Navigation lib no go for us.

So current situation:
- Navigation library is already released with stable API.
- API is created without test-ability in mind. Huge classes with large amount of public methods, no interfaces. Using such tools as Mockito is not a solution, but workaround for situations when API is not testable.

After 10 years of creating un-testable Android SDKs there was possibility to have clean slate opportunity. And here we go again. API released and needs to be maintained now. Please recognize this problem now and bump priority from lowest (P3) to something higher. Because until we won't have possibility to test our app navigation flows we can't use this library.