Gradle: No tests found

Question

When I am trying to run Android tests by executing:

./gradlew connectedDebugAndroidTest

The following error occurs:

com.android.builder.testing.ConnectedDevice > No tests found.[devicename] FAILED
No tests found. This usually means that your test classes are not in the form that your test runner expects (e.g. don't inherit from TestCase or lack @Test annotations).
:connectedDebugAndroidTest FAILED

FAILURE: Build failed with an exception.

I have not made any changes to build.gradle or gradle-wrapper.properties files.

The issue can't be solved by updating everything to the latest version (gradle, android plugin, build tools, etc.)

All tests were previously successful. What could cause this mystic regression? Thanks.

It sometimes happens to me too, which means it's time to clean project. — azizbekian, Mar 27 '17 at 08:51
@azizbekian the funny thing is that nothing has changed. I cleaned the project several times. — Andrii Abramov, Mar 27 '17 at 09:08

score 68 · Accepted Answer · answered Oct 02 '17 at 22:13

68

One possible reason for this error message is that you get a crash in the app early in the test Runner. In such cases the exception stack will be in logcat but not in the gradle output.

answered Oct 02 '17 at 22:13

miguel

16,205
4
53
64

Indeed, this was the case. Thank you! – azizbekian Oct 21 '19 at 12:50
@Miguel you are right. This crash seems random, it happens sometimes but not all the time with no condition changes. Any way to ensure it doesn't happen at all? – saintjab Feb 20 '20 at 12:43

score 6 · Answer 2 · answered Apr 12 '17 at 10:44

6

I had the issue, try upgrading the test runner. Upgrading it to 0.5 from 0.4.x solved it. Ensure you have these lines in your build.gradle:

androidTestCompile "junit:junit:4.12"
androidTestCompile "com.android.support.test:runner:0.5"

answered Apr 12 '17 at 10:44

jonduran

61
1

score 2 · Answer 3 · answered Jun 17 '19 at 22:02

I faced this exact issue today. Please do feel free to use all the other worthy solutions as mentioned above but what specifically worked for me was to delete the ".gradle" folder (found under the project panel on the left in Android Studio) entirely, followed by a clean build. A simple clean build didn't work for me.

score 0 · Answer 4 · answered Apr 07 '21 at 15:05

0

This can happen if the tests are placed in the test or androidTest directory without a package. The path should be something like /src/androidTest/kotlin/yourPackageName/yourTestClass.

answered Apr 07 '21 at 15:05

Brian Bethke

154
6

score 0 · Answer 5 · answered Sep 07 '21 at 19:11

0

You can check if individually, all tests pass. Could be some test(s) is(are) failing. Had a similar issue and that was my case

answered Sep 07 '21 at 19:11

zeffah

21
4

davormaricdev · Answer 6 · 2019-08-05T16:15:23.183

-3

I solved this by deleting androidTests folders from unneeded modules - /common and /data in my case.

edited Aug 05 '19 at 16:15

answered Aug 05 '19 at 11:42

davormaricdev

20
3

Deleting the tests is not a solution – Louis Nov 23 '20 at 08:32

Gradle: No tests found

6 Answers6

Linked