Reputation: 18593

Why is the Android test runner reporting "Empty test suite"?

I am banging my head against the wall here trying to figure out why IntelliJ/Android is reporting "Empty test suite". I have a small project with two IntelliJ Modules ("Projects" in Eclipse). The Unit test module has its own AndroidManifest.xml, which I have pasted at the bottom. I am trying to run an ActivityUnitTestCase, since the tests will be dependent upon the Context-object.

The package name of the main module is nilzor.myapp. The pacakge name of the test module is nilzor.myapp.tests

Why is not the test runner detecting the testBlah()-method as a test?

<?xml version="1.0" encoding="utf-8"?>
<!-- package name must be unique so suffix with "tests" so package loader doesn't ignore us -->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
          package="nilzor.myapp.tests"
          android:versionCode="1"
          android:versionName="1.0">
    <!-- We add an application tag here just so that we can indicate that
         this package needs to link against the android.test library,
         which is needed when building test cases. -->
    <application>
        <uses-library android:name="android.test.runner"/>
    </application>
    <!--
    This declares that this application uses the instrumentation test runner targeting
    the package of nilzor.myapp.  To run the tests use the command:
    "adb shell am instrument -w nilzor.myapp.tests/android.test.InstrumentationTestRunner"
    -->
    <instrumentation android:name="android.test.InstrumentationTestRunner"
                     android:targetPackage="nilzor.myapp"
                     android:label="Tests for nilzor.myapp"/>
</manifest>

And here is my test class:;

package nilzor.myapp.tests;

public class NilzorSomeTest<T extends Activity> extends ActivityUnitTestCase<T>{
    public NilzorSomeTest(Class<T> activityClass){
        super(activityClass);
    }

    @SmallTest
    public void testBlah(){
        assertEquals(1,1);
    }
}

I have read the testing fundamentals, the activity testing document, and tried following this Hello world test blog, even though it is for Eclipse. I cannot get the test runner to find and run my test. What am I doing wrong?

Some of the questions I still feel unsure about are:

Do I need an Annotation above the Unit test method?
Do I need to prefix the method with "test", or is that just for JUnit tests?
Can I have tests in sub-packages of nilzor.myapp.tests?

But the main question of this post is why does not the test runner detect my test?

Upvotes: 98

Answers (30)

Vaios

Reputation: 567

I had the following block of code

@get:Rule
lateinit var activityScenario: ActivityScenario<HomeActivity>

because i needed to pass different parameters in the intent of activity based on the different test cases. When i removed the @get:Rule the tests started to work again.

Upvotes: 0

xavierdominguez

Reputation: 99

Not a solution but a workaround that will get you back on track quickly:

Firstly, find a test that works. I was writing a new test where I got the 'empty test suite' error. I ran other tests and they were working as usual.
Copy the test file that does work. Run it to make sure this copy works like the original.
Remove the body and replace it with your new test code.

The test should now work.

We spent about two hours trying to find the cause but to no avail.

Upvotes: 0

Mihir

Reputation: 56

I had this happen to me when I mistakenly marked a non mock class variable with the annotation @Mock Removed the annotation and the tests ran successfully. This happened with Junit 4.5 on Android Studio

Upvotes: 0

Jeff Stapleton

Reputation: 301

I had a similar issue. Not sure why this is occurring but I was able to fix it by going to: "File" > "Invalidate Caches/Restart" in Android Studio.

Upvotes: 7

lmac

Reputation: 774

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);
    }
}

about your other questions:

No. My tests still run without any annotations, but I guess it's a good practice to have them. It allows you to specify size of tests to run. See What is the purpose of @SmallTest, @MediumTest, and @LargeTest annotations in Android? for more detail.
Yes, you need "test" prefix. InteliJ gives "method never used" warning when there's no "test" prefix, and skips that method during test run.
Yes. I have my tests organized into subpackages and it seems to be working well.

Upvotes: 70

Francisco Junior

Reputation: 2016

After facing the problem today - not being able to run the instrumented android tests with Empty suite error - I found a git issue about this problem and thanks to Stephan Linzner, I could run the tests.

tl;dr You have to right click the test package and not the class in order to make the tests run.

Reference: https://github.com/googlecodelabs/android-testing/issues/27#issuecomment-219074863

Upvotes: 1

shocking

Reputation: 908

My issue was caused by an exception being thrown in the @BeforeClass method of my test case. It some how wasn't causing the test to fail - I only found it by inspecting the logcat output.

I fixed the exception and suddenly my tests were running!

Upvotes: 1

Juan José Melero Gómez

Reputation: 2789

In my case, I had my instrumented tests in androidTest/java/<package.name>/MyTestingClass, but I had set my current build variant to "preproduction". And there's the point! As specified in Android Studio documentation:

By default, all tests run against the debug build type.

The message Class not found. Empty test suite. kept appearing until I did this:

Add this line to my build.gradle:

android{
    [...]
    testBuildType "preproduction"
}

Synchronised gradle.
Delete my previous test configurations since they don't take this Gradle synchronisation into account.

Then I executed the tests again and this time they run just perfect!!!

Upvotes: 0

Pablo

Reputation: 642

I had this problem because I had this in my build.gradle:

testOptions {
    execution "ANDROID_TEST_ORCHESTRATOR"
}

Even though I wasn't using the Android Test Orchestrator (must have copyied from the tutorials by mistake).

Commenting that out solved it for me.

Upvotes: 3

Laurent

Reputation: 1739

I was doing some insertions in a db in the @BeforeClass method. I realised I had an object/database mapping problem. This data mapping problem was the cause of this issue for me.

Upvotes: 0

Janin

Reputation: 306

I had the same issue, and the reason was my test class did not have Test at the end of the class name!

Upvotes: 1

Will P

Reputation: 429

I experienced the "Empty test suite" error when trying to run local unit tests in my Android Studio 3.0 project.

After reading the Android Developer documentation, I quickly realised that the issue was caused by my gradle config which included the following lines.

testImplementation 'com.android.support.test:runner:0.5'
testImplementation 'com.android.support.test:rules:0.5'

The AndroidJUnitRunner class is a JUnit test runner that lets you run JUnit 3- or JUnit 4-style test classes on Android devices.

Since my tests were local and therefore not required to run on any device, removing the above com.android.support.test... entries enabled me to execute the unit tests.

Upvotes: 0

ka3ak

Reputation: 3191

The accepted answer didn't solve my problem. So I decided to copy ExampleInstrumentedTest which is created by default in Android Studio and runs without any problems, renamed it during the copy process (no Refactor->Rename after copying!) and pasted the contents of my unit test into it. After that the error disappeared.

Upvotes: 0

Beloo

Reputation: 9925

In my case that problem was caused due to mistake in my code, actually that was in application class, so target activity wasn't opened and test output prints

Empty test suite error

I have tried run tests directly from terminal with adb shell am instrument -w -r -e package your.package -e debug false android.support.test.runner.AndroidJUnitRunner. With this it prints for you much more about exception.

Upvotes: 2

Sylvain

Reputation: 113

Obviously, you need a target device as to run your tests as they are instrumented tests. For some reasons, Android studio sometimes does not ask you to point to this target device and just prompt the "Empty Test Suite" message. There are different ways to fix this, here are a few :

run your main app and select a target device or
go to the Run (Run/Run.../Edit Configurations) configuration and modify the Deployement Target Options

Upvotes: 3

Lyn

Reputation: 291

I just renamed the file and the problem fixed.

Upvotes: 1

Andrea Thacker

Reputation: 3470

I had the same issue on Android Studio 2.3.1, turns out it was just a bug with AS. Running the same test on version 2.2.1 performs fine.

If you're only running Android Studio on the Cannary channel, I recommend you also install a stable version as well. http://tools.android.com/tips/using-multiple-android-studio-versions

Upvotes: 4

Mateus Gondim

Reputation: 5532

In my case, none of the previous answers worked. The solution was to simply move the test class to another package.

This happened under androidTest/

Upvotes: 2

Psijic

Reputation: 992

In Android studio with spock framework I've changed my gradle's version from 2.2.2 to 3.2.1 and all goes well.

Upvotes: 0

Gary Davies

Reputation: 960

I did nothing and the problem went away after half a day of pain, I opened and closed the projects many times, ran each class tests manually, maybe that fixed my it.

Upvotes: 0

HRVHackers

Reputation: 2873

Here are my debugging steps I go through when Android Studio all of a sudden decides to stop running / debugging tests (And boy does this happen embarassingly often!!):

Build: → Rebuild project
Restart Device: Restart your device/emulator and try again
Device switch: if you have both a regular phone and an emulator unplug one and try running it with just one of the devices
Android Studio: File--> Invalidate caches and restart
Activity Monitor / Task Manager: sort processes by name, see if there is a nameless processes that's using up a lot of ram, this is a "ghost" process from Android studio that must be killed
git revert: try stashing /reverting your latest code. Sometimes there is a compile error that Android Studio / gradle misses and it will just try to run uncompilable code.
Uninstall then reinstall Android Studio.

I will add more fixes as I run into them!

Upvotes: 0

serv-inc

Reputation: 38207

None of the above fixed it for me. What helped was following the instructions:

Create a test configuration

In Android Studio:

Open Run menu -> Edit Configurations

Add a new Android Tests configuration

Choose a module

Add a specific instrumentation runner:
  android.support.test.runner.AndroidJUnitRunner
Run the newly created configuration.

Upvotes: 10

Jorge Salas

Reputation: 141

In my case, the project I was working on had a couple of modules. None of the solutions I found for this error helped me, and then somehow I realized that if I added the testing dependencies in BOTH of the build.gradle files, the tests magically started working. It doesn't matter if your tests live in only 1 of the modules, both gradle files must include the dependencies and the testInstrumentationRunner value.

So, if like me, none of the other answers have helped you, try adding these lines to the build.gradle file of each of your modules:

android {    
    ....
    defaultConfig {
        ...
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }  
}

and then also add:

dependencies {
    ...
    // Test
    androidTestCompile 'com.android.support:support-annotations:23.4.0'
    androidTestCompile 'com.android.support.test:runner:0.5'
    androidTestCompile 'com.android.support.test:rules:0.5'

}

Upvotes: 1

tir38

Reputation: 10421

If this is happening "all of a sudden" or "it was working 5 minutes ago" my solution was to go into Run/Debug configurations and remove any configurations under "Android Tests". Sometimes these configurations get corrupted if I refactor the class under test (for example by moving to an new package).

Upvotes: 55

petertc

Reputation: 3911

The test class may excluded from the compilation. Fix it in setting-compiler-exclude.

Upvotes: 0

cdaringe

Reputation: 1538

I had a raw Java project where this was occurring. Simply Java + JUnit4. It definitely resides with something in your .idea/ or .iml files. I scrapped mine, re-imported, and finally the tests ran again.

Upvotes: 0

kotlinski

Reputation: 330

I don't know if it helps for Android Studio, but I had some kind of Intellij-Gradle conflict. Solved it by "right-clicking" on the test-file and hit "compile file ...Test.java". After that I could run single tests again.

Upvotes: 4

Phil

Reputation: 36289

None of the other solutions worked for me, but I was able to get this working simply by uninstalling the existing app or test suite, then running the tests.

Upvotes: 1

Marquis Blount

Reputation: 8105

For Intellij 15 I resolved this issue by:

Opening the 'Project Structure' settings
Clicking 'Modules' (on left)
'Sources' Tab
a. Right click on your source directory (usually src) click 'Source'.
b. Right click on your test directory click 'Test'
c. Right click on your out directory click 'Excluded'
Go to 'Paths' tab
a. Click 'Use module compile output path' radio button
b. Select your output path directory for 'Output Path'
c. Select your test path directory for 'Test output Path'
Click Ok

Upvotes: 3

Pratik Mandrekar

Reputation: 9568

I had tests that were running fine until gradle and android studio got upgraded.

Apart from adding a default constructor to your tests, you might need to do some of these things to get your test suite to work

Under src/ create androidTest/java/<your-package-name>/test . Note the androidTest. Anything else including instrumentTest will not work.

Add this to build.gradle

sourceSets {
    testLocal {
        java.srcDir file('src/androidTest/java')
        resources.srcDir file('src/androidTest/resources')
    }
}



android{
    sourceSets {
       instrumentTest.setRoot('src/androidTest/')
    }
}

dependencies{
     testLocalCompile 'junit:junit:4.11'
}

task localTest(type: Test, dependsOn: assemble) {
    testClassesDir = sourceSets.testLocal.output.classesDir

    android.sourceSets.main.java.srcDirs.each { dir ->
        def buildDir = dir.getAbsolutePath().split('/')
        buildDir = (buildDir[0..(buildDir.length - 4)] + ['build', 'classes', 'debug']).join('/')

        sourceSets.testLocal.compileClasspath += files(buildDir)
        sourceSets.testLocal.runtimeClasspath += files(buildDir)
    }

    classpath = sourceSets.testLocal.runtimeClasspath
}

check.dependsOn localTest

Add this to the AndroidManifest.xml

 <instrumentation
        android:name="android.test.InstrumentationTestRunner"
        android:label="Tests for my packaged app"
        android:targetPackage="<my-package-name>.test" />

Upvotes: 3

Why is the Android test runner reporting &quot;Empty test suite&quot;?

Answers (30)

Related Questions

Why is the Android test runner reporting "Empty test suite"?