IssueTracker

Test Support Runner 1.0, Espresso 3.0.0 (com.android.support.test.runner).

What steps will reproduce the problem?
1. Update Test Support Runner from 0.5 to 1.0
2. Run tests
3. Observe that test run fails with NoClassDefFoundError if test or app apk references non-existing classes

How are you running your tests (via Android Studio, Gradle, adb, etc.)?
./gradlew connectedAndroidTest, Composer (https://github.com/gojuno/composer), Firebase Test Lab, Android Studio.

What is the expected output? What do you see instead?

Tests should run normally.

See, in Java it's fine to reference a class that is not presented on classpath, because actual interaction with class can be hidden behind condition ie "if" or even not happen at all, you can also implement/extend interfaces/classes that are not on the classpath if you don't interact with such classes in your code.

In our case we see that test runner fails because some of our classes reference:

- javax.annotation.processing.AbstractProcessor
- dagger.internal.codegen.GraphAnalysisProcessor

Stacktrace is attached to the issue.

Moreover, if we run tests with Runner 1.0 on Firebase Test Lab, Firebase TC will mark test run as SUCCESSFUL while in fact it fails right away.

That was also mentioned in https://issuetracker.google.com/u/1/issues/37133798, but Runner 0.5 did not fail the test run, it just printed it as instrumentation problem.