android / android/architecture-samples

Dagger Android with Android Test Orchestrator casues "Test framework quit unexpectedly"

Open
#719 1 comment 4 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
45.8k
Forks
11.9k
PR merge metrics
No merged PRs in 30d

Description

In Dagger Android example, when changed the testOptions to use [Android Test Orchestrator](https://developer.android.com/training/testing/junit-runner)
```
testOptions{
execution 'ANDROIDX_TEST_ORCHESTRATOR' // <- add this
unitTests{
includeAndroidResources = true
all {
testLogging {
events 'passed', 'skipped', 'failed', 'standardOut', 'standardError'
}
}
}
}
```
then run instrumented tests, the tests will executed on the device but in android studio it will report
Test framework quit unexpectedly.

This is probably due to using the CustomTestRunner that extends AndroidJUnitRunner?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Dagger Android example with Android Test Orchestrator enabled, then inspect the CustomTestRunner and the instrumented-test configuration. Compare the runner behavior with the Android Test Orchestrator requirements; done means the instrumented tests run and Android Studio no longer reports that the test framework quit unexpectedly.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.