IssueTracker

In addition, it is particularly annoying that it is documented to use debugImplementation("androidx.fragment:fragment-testing:XXX") here and kind of enforced by a lint warning, whereas this document insists on implementation("androidx.fragment:fragment-testing:XXX"), which is actually necessary anyway if you want ./gradlew compileReleaseUnitTestKotlin to compile.

I've had to disable release unit tests for any modules that depend on fragment-testing, since our project relies on passing the gradle check task before builds (which builds both debug and release variants).

gradle.taskGraph.useFilter { task ->
    if (task.name.startsWith("test") && task.name.contains("ReleaseUnitTest")) {
        return false
    }

    return true
}

We have a project that has multiple modules. In our code.dependencies.gradle which is applied to all build.gradle files, and using fragment-testing version 1.2.5, I've tried the above solution and I still get test framework quit unexpectedly. I've also tried using implementation and androidTestImplementation, but still doesn't work.

This issue still mentioned on page 8 of https://developer.android.com/codelabs/advanced-android-kotlin-training-testing-test-doubles, any updates?

Wrote a post on how to get fragment tests to work in the jvm without breaking release builds. Essentially just add a junit assumption to skip fragment tests if it's not a debug variant:

    @Before
    fun setup() {
        assumeTrue("Skipping non-debug test", BuildConfig.DEBUG)
    }

Any update would be appreciated :)

For a bit of context: The androidx.fragment:fragment-testing library declares an activity named androidx.fragment.app.testing.FragmentScenario$EmptyFragmentActivity in its AndroidManifest.xml file. The problem is that activities defined in a project's androidTest/AndroidManifest.xml file or in the AndroidManifest.xml file of any of the project's androidTestImplementation dependencies are not merged into the project's main AndroidManifest.xml file and therefore not available for use in the instrumentation tests. This, I believe, is the reason why the androidx.fragment:fragment-testing library has to be declared as a debugImplementation dependency instead of an androidTestImplementation dependency.

It would be great if Android testing offered a way for manifest entries defined in the project's androidTest/AndroidManifest.xml file or in the AndroidManifest.xml file of any of the project's androidTestImplementation dependencies were available for use in the instrumentation tests.

Unfortunately, there is nothing we can do about this. And modifying for test code will continue to be required.

Could a separate fragment-testing-manifest artifact be shipped that only defines the Activity manifest entries? That way only the manifest get merged into non test code, and not fragment-testing and all its test dependencies like androidx.test.core.

This is how we worked around similar issues in androidx.test.core

I'd be willing to take this on if the androidx.fragment maintainers agree with this approach.

See https://github.com/android/android-test/issues/1587 for a recent re-manifestation of this issue.

In Fragment 1.6.0-alpha04, we've added a new fragment-testing-manifest artifact. This means that instead of adding fragment-testing as a debugImplementation, you can now instead add fragment-testing-manifest as a debugImplementation and keep fragment-testing as androidTestImplementation.

debugImplementation "androidx.fragment:fragment-testing-manifest:$fragment_version"
androidTestImplementation "androidx.fragment:fragment-testing:$fragment_version"

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.fragment:fragment-testing:1.6.0-alpha04

Please file a new bug with a minimal project that reproduces the issue.