Android studio says "Empty Test Suite" for AndroidTestCase [duplicate]

Since nobody else mentions it: methods in AndroidTestCase subclasses need to be public and have names starting with "test"!

The OP and the answers all got this right but I missed it and got the exact same error.

I got this error when running tests from Android Studio. Turned out I had placed my test cases in the wrong folder. When running Gradle/Android Studio, all Android tests should be in the folder src/instrumentTest/java.

Edit: In Gradle plugin version 0.9 or later the correct name of the folder is androidTest. (http://tools.android.com/tech-docs/new-build-system/migrating_to_09)

I understand that this question is old, and the development tools have changed significantly since this question has been asked.

However, I had a similar issue (in AndroidStudio 2.1.1) and it turned out that it was just the error message that was quite misleading. For me it said:

Test running started Test running failed: Instrumentation run failed due to 'java.lang.IllegalStateException' Empty test suite. 

(Note: The difference to the original question is in IllegalStateException vs. RuntimeException)

It turned out that this IllegalStateException was actually thrown in the initialization of the application context as can be seen by inspecting the logcat output. As a result, no test-methods were run, and Android Studio writes this somewhat misleading "Empty test suite" error.

I.e. "Empty test suite" can mean what it actually says (you don't have any test methods declared, e.g. because you forgot to annotate them with @Test), but it can also mean that something (like a runtime exception thrown in your application initialization code) prevents the test-runner from reaching any test methods (which seems to be your case).

Check adb-logcat and search for RuntimeExceptions. This will probably find you the root-cause of your problem.

I got this error because one of my test methods didn't include "throws exception" after the method signature. might help somebody

I got the same issue. I was having testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" in my defaultConfig {...}. I have just removed that line, and now it's working fine (The IDE is picking the right runner config on build time).

I hope this will help someone.

My problem was I had default constructor generated by android studio, looked like this

public class SomeTest extends ActivityUnitTestCase<ActivityYouWantToTest>{ public SomeTest(Class<NewsActivity> activityClass) { super(activityClass); } } 

and I had to change it to this to get rid of the problem

public class SomeTest extends ActivityUnitTestCase<ActivityYouWantToTest>{ public SomeTest() { super(ActivityYouWantToTest.class); } } 

We use the AndroidTestCase class to define that we are testing components which are specific to Android. The main benefit of AndroidTestCase is that it gives us access to the application's Resources such as strings and layouts, etc.

The AndroidTestCase does not require you to overwrite the default constructor as it does not provide a particular Activity as the Context, but rather provides you a general one so you can still call getContext().

In your example, you are not using any Android components, so for you, the following would make sense:

import android.test.suitebuilder.annotation.SmallTest; import junit.framework.TestCase; public class DateFormatTest2 extends TestCase { @SmallTest public void testMultiply() { assertEquals("10 x 5 must be 50", 50, 10 * 5); } } 

Notice the use of TestCase rather than AndroidTestCase.

For AndroidTestCase to be applicable, a test that requires resources would be necessary:

import android.test.AndroidTestCase; import android.test.suitebuilder.annotation.SmallTest; public class DateFormatTest extends AndroidTestCase { @SmallTest public void testAppTitle() { assertEquals("MyApp", getContext().getResources().getString(R.string.app_name)); } } 

Here we use the AndroidTestCase because we need to access the application's resources.

This guide might help - http://www.slideshare.net/tobiaspreuss/how-to-setup-unit-testing-in-android-studio

On the latest gradle (0.9+) the test should be under androidTest dir

Also in your gradle.build:

dependencies { androidTestCompile 'junit:junit:4.+' } 

also add those under defaultConfig {

testPackageName "test.java.foo" testInstrumentationRunner "android.test.InstrumentationTestRunner" 

}

Did you configure your testRunner in your gradleConfig? We use different TestRunners for different tests (to speed things up. My config looks like this

android { // Some stuff defaultConfig { // Some other stuff //junit test testInstrumentationRunner "de.qabel.qabelbox.QblJUnitRunner" //ui tests testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } } 

If i disable one of this lines the corresponding test will also report "Empty Test Suite".

I just started learning about testing Android applications and I've been struggling with the same problem. You need to provide default constructor for your test class, for example:

package nilzor.myapp.tests; public class NilzorSomeTest extends ActivityUnitTestCase<ActivityYouWantToTest>{ public NilzorSomeTest(){ super(ActivityYouWantToTest.class); } @SmallTest public void testBlah(){ assertEquals(1,1); } } 

I already have a default constructor in my test case but still it was giving me error "Empty test suite" and was stuck at "Instantiating tests...".

Tried creating new workspace, resetting Android Studio, but that didn't work.

Finally, close Android SDK and emulator.

1. Go to your android-sdks/platform-tools.

2. Clear all Android temp files with these commands:

   a. rm -rf ~/Library/Application Support/AndroidStudio

   b. rm -rf ~/Library/Caches/AndroidStudio

   c. rm -rf ~/Library/Application Support/AndroidStudio

   d. rm -rf ~/Library/Preferences/AndroidStudio

3. Run:

   ./adb kill-server ./adb start-server 

4. Start Android and run test case.