IssueTracker

Component used: Fragment
Version used: 1.1.0 (and most others)
Devices/Android versions reproduced on: N/A

The logical way that a developer would choose to add fragment-testing into the androidTest configuration is with:

    androidTestImplementation "androidx.fragment:fragment-testing:1.1.0"

but this is invalid for Espresso Tests, because fragment-testing includes an EmptyFragmentActivity class that is used to bootstrap the FragmentScenario. That Activity must exist in the runtime application's Manifest, and it cannot be in the androidTest manifest because those activities can only start in the instrumentation process, not the application's process. Therefore the documentation <https://developer.android.com/training/basics/fragments/testing> says that to add the dependency the project should add:

    debugImplementation "androidx.fragment:fragment-testing:1.1.0"

There is an open issue to improve the documentation to clarify why it needs to be debugImplementation and not androidTestImplementation, and to call it out as an explicit requirement (so it cannot be perceived to be an oversight). That issue is: https://issuetracker.google.com/issues/119070777

But to better catch this common error, it would great to have a Lint check that will fail if a project tries to include the fragment-testing artifact in the androidTest configuration, when it should instead be debugImplementation.