Open GoogleCodeExporter opened 9 years ago
Original comment by nkors...@google.com
on 5 May 2015 at 5:32
Hi there,
It's not the first time I see this problem after changing dependencies and it
usually only happens from Android Studio. It looks like a problem with the
Gradle plugin but it's hard to reproduce.
First, change back to espresso-core:2.1 and execute
./gradlew clean connectedCheck
from command line.
Original comment by jalc@google.com
on 6 May 2015 at 10:54
Hi,
Getting same issue here with same config, but I'm setting up espresso 2.2 from
scratch on the same module as the app project. I'm trying to run a sample test
and I get this:
Test running started
Test running failed: Unable to find instrumentation info for:
ComponentInfo{test/android.support.test.runner.AndroidJUnitRunner}
Empty test suite.
My environment is:
Android Studio 1.2.2 on a Mac
jdk1.7
gradle 2.2.1
target sdk 22
dependencies:
test runner:0.3
espresso-contrib:2.2
espresso-core:2.2
Original comment by fernanda...@gmail.com
on 26 Jun 2015 at 4:32
Just adding the dependency espresso-contrib:2.2 to a working test caused the
"Empty test suite" issue.
The following dependency definition solved the issue:
androidTestCompile('com.android.support.test.espresso:espresso-contrib:2.0') {
exclude group: 'com.android.support', module: 'support-annotations'
exclude group: 'com.android.support', module: 'appcompat'
exclude group: 'com.android.support', module: 'support-v4'
exclude module: 'recyclerview-v7'
}
Thanks to elcolto at StackOverflow: http://stackoverflow.com/a/30715011/4137032
Original comment by pamtb...@gmail.com
on 9 Sep 2015 at 2:25
Original comment by slinz...@google.com
on 15 Sep 2015 at 10:58
Original issue reported on code.google.com by
mshu...@netflix.com
on 24 Apr 2015 at 7:13