I have been tasked with adding Snapchat login to our Android app. Great, I've got it integrated and the login works (after some faffing about configuring it).
However, after I opened my PR, our CI flagged that the connectedAndroidTest task was failing with the following message:
com.android.build.gradle.internal.testing.ConnectedDevice > No tests found.[Pixel_XL_API_26(AVD) - 8.0.0] 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).
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':<app_name>:connectedDebugAndroidTest'.
> There were failing tests. See the report at: file:///C:/Users/<my_username>/StudioProjects/<project_name>/<module_name>/build/reports/androidTests/connected/index.html
I opened the report file, and it also stated that there were no tests found.
I have not touched, updated, opened or even dreamt about any test files whilst implementing this feature, and have certainly not changed anything about testing in our code base.
To prove this, I checked out dev, and ran the connectedAndroidTest command from there, they all passed. Then, I simply added the following snapchat dependencies to the gradle file on dev:
implementation 'com.snapchat.kit.sdk:login:1.6.5'
implementation 'com.snapchat.kit.sdk:core:1.6.5'
Synced the project with gradle, and then ran the connectedAndroidTest command again. This time, the tests fail with the "No tests found" error. So, no code change from me, just simply adding the snapchat dependencies is causing this issue.
What. On. Earth.
Really? Ok, so I've been pulling my hair out, scouring google for any advice and I've so far found nothing. So, I turn to StackOverflow; has anyone ever come accross such an issue? Any advice on how to start debugging and fixing this madness?
EDIT:
I have created a brand new, completely empty project, and can replicate this easily by just adding the snapchat dependencies.
Apparently when an apk is built for the instrumentation tests, it's missing some meta tags that are needed by the snapkit SDK
Adding an AndroidManifest.xml under the androidTest directory with only the following contents (even a not real client-id) resolves the issue.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="your.app.package">
<application>
<meta-data android:name="com.snapchat.kit.sdk.clientId" android:value="dummy-snapchat-client-id" />
</application>
</manifest>
If you need to write tests that will use the snapchat SDK maybe you will need to provide your real client-id and any other meta-tags your normal AndroidManifest has
When I run a Andriod test (junit) test in Android Studio I get the folowing errormessage.
Exception in thread “main” java.lang.NoClassDefFoundError: junit/textui/ResultPrinter.
I assume the error is because it cannot find the junit.jar file.
When I follow below junit setup it does not fix the error:
http://www.tutorialspoint.com/junit/junit_environment_setup.htm
I cannot get above setup working. It still cannot find the junit classes.
Any ideas how to fix the problem.
Did you put your test class in correct place in the folder structure, Martin?
Look at the table under "Flavors and build types support" on http://tools.android.com/tech-docs/unit-testing-support
It resolved the issue for me, but I had to move the test class (and create folders) manually - while Android Studio can generate the test suite automatically for you (Go to... Test, after right-clicking on the class header), it doesn't offer to put it in right location by default, so it can be confusing.
Also make sure to set Test Artifact to "Unit Tests" in Build Variants tab, but the official tutorial says that more explicitly so I assume that's not what you overlooked.
I understand your question was dated, but maybe someone stumbles upon it like I only just did struggling with this issue myself ;) And guys, remember - highest voted answers on StackOverflow that tell you to stick to Android tests and drop JUnit are obsolete now, Android Studio supports JUnit tests that run on your PC directly, as explained in the link I posted above. Of course they don't give you access to instrumentation - I use them to test my "pure" Java logic which is platform agnostic.
So I'm trying our Android Studio and testing a project that worked in eclipse. I got everything compiling and the application will launch just fine, but I can't get my unit tests up and working. I eventually got them compiling by adding my applications lib folder as a dependency, but I don't think my run configuration is right because whenever I run my tests I get this error
Installing <packagename>
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/<packagename>"
pkg: /data/local/tmp/<packagename>
Success
Running tests
Test running started
Test running failed: Unable to find instrumentation info for: ComponentInfo{<packagename>/android.test.InstrumentationTestRunner}
Empty test suite.
Edit: To all new arrivals, the state of Android Studio has changed a lot since I initially posted this question, but many helpful people have continued to post their particular solution for this error. I'd advise sorting by active and checking out the newest answers first.
If you have a testInstrumentationRunner defined in your build.gradle such as this:
android {
defaultConfig {
testInstrumentationRunner "com.google.android.apps.common.testing.testrunner.GoogleInstrumentationTestRunner"
make sure that in the run configuration window you use the exact same "Specific instrumentation runner" in your Android Studio / IntelliJ run configuration for your test.
In my case, the solution was:
View > Tool Windows > Build Variants
Select a *Debug variant
Explanation and solution
This error "Unable to find instrumentation" appears if targetPackage declared in the manifest of the test application is different from the package declared in the manifest of the application being tested:
Application being tested:
<manifest package="com.example.appbeingtested" … >
Test application :
<instrumentation
android:name="android.test.InstrumentationTestRunner"
android:targetPackage="com.example.appbeingtested" … />
I solved this problem by changing
android.test.InstrumentationTestRunner
into
com.android.test.runner.MultiDexTestRunner
in EditConfigurations -> Specific Instrumentation Runner (optional) tab.
Turns out, because my app is using MultiDex, I need to change test runner to MultiDexTestRunner as well.
UPDATE:
As #dan comment, InstrumentationTestRunner is deprecated use AndroidJUnitRunner instead.
In my case the Run/Debug Configurations were wrong.
One Solution:
Go to Run/Debug Configurations
Run -> Edit Configurations...
Setup a Android-Test for your test class
Select your Android test configuration on the left side or create a new one with the plus icon and name it e.g. ClassNameTest
Select the module containing your test class. In the simplest case the test class is in your app module so select app.
Select on the next row your test configuration. I use:
Class: to run all tests of one class.
Choice your test class
Finally configure your target device and select ok.
This only works in AndroidStudio Version < 2.3
In my case the wrong instrumentation runner was selected.
I fixed this by specifying the instrumentation runner in the Run/Debug Configuration of the test (see below). There you can select a runner from the list.
You find the Run/Debug Configurations: Run -> Edit Configurations ...
It seams you have not good project structure.
Open AndroidManifest.xml and check does it have
<instrumentation android:name="android.test.InstrumentationTestRunner"
android:targetPackage="com.example.YourClass"
android:label="Tests for com.example.YourClass"/>
If NO do next:
Reorganize your directory structure to the following one: (this is the recomendation from official source)
MyProject/
AndroidManifest.xml
res/
... (resources for main application)
src/
... (source code for main application) ...
tests/
AndroidManifest.xml
res/
... (resources for tests)
src/
... (source code for tests)
You see that you need to have inner tests module. For creating it in Idea IDE do next File -> New Module -> Test Module. After creating you can see one new AndroidManifest.xml. And it has instrumentation declaration inside.
I've got same problem as #Iuliia Ashomok and tried everything on the internet.
Still no luck.
After 2 days investigation, I found that the problem is created by the mobile phone. .V.
I originally use Xiaomi Mi4i as testing device(rooted) and tests could not be run. Of course, I got the error below.
Test running failed: Unable to find instrumentation info for: ComponentInfo{<packagename>/android.test.InstrumentationTestRunner}
However, when I use Sony Xperia Z3(No root), everything works well.
I once got this error. I use the sdk tools in CLI mode. And the error happened when i launch 'ant test' in the test project. I later notice that I didn't even build and install the test project before ! (with 'ant debug install')
So you should have try to check your running configuration to see if the test project got effectively build before running the test.
For the other case, Android Studio use Gradle. I don't know it well but try to check the Gradle settings for the project or the Gradle settings file.
For me the problem was having this dependency:
debugCompile 'com.android.support.test:rules:0.2'
After I removed it my tests were found and run again.
Note that I didn't get the "Unable to find instrumentation" message but a "No tests found" message.
It turned out to be a delay problem. It fixed automatically after I waited a while reading the Internet solutions. I recompiled the code, and it worked.
Since none of these answers helped me, I wanted to share my solution for anyone who is as desperate as I was. :)
Because of the testing libraries that I was using, I needed to enable multidex support by adding multiDexEnabled true to my Gradle build. I'm not sure I had multidex support fully implemented to begin with (the proper way of doing it has changed since I last implemented it) but ultimately, I didn't end up needing it and removing that line from my build fixed the error. My team at work has had a few testing issues related to enabling multidex support… in typical Android style.
In my case in same classes some test cases were picking correct test runner ( android.support.test.runner.AndroidJUnitRunner ) which was defined in build.gradle, and some test cases were picking up android.test.InstrumentationTestRunner, which was not defined at least in Manifest or build.gradle or edit configuration. Ideally it should have been resolved by Sync Project with Gralde option, though it didn't work.
At last I found wrong test runner defined against a method in .idea/workspace.xml, I changed it manually, and issue got resolved.
Generally we are not supposed to edit this Android Studio generated file, but for me it did worked as last option.
In my case, the issue was in device too. Other devices were working fine. Simple uninstall and reinstall fixed it.
This answer is going to explain the history issues and summarise all related settings.
Basically there are 3 possible places for instrumentation test runner configurations.
In EditConfigurations -> General tab -> Specific Instrumentation Runner (optional)
This is existing in Android Studio 2.2 and version before only, in latest version, it is removed already.
In manifest file, the test runner is configured as below.
< instrumentation android:name="android.support.test.runner.AndroidJUnitRunner"
android:targetPackage="com.mytestapp.test"/>
Since "android.test.InstrumentationTestRunner" is deprecated in API level 24, this setting is also not necessary already, as long as you configure the runner in gradle file.
If you want to keep this setting, please make sure the runner name should match to the one you set in the gradle file, otherwise you will got this error also.
In gradle file.
This is the only recommended way if you use Android Studio v2.3 above.
android {
.......
defaultConfig {
.......
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
}
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?
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.
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).
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.
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.
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.
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
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" />
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
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
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.
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/
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.
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.
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'
}
I just renamed the file and the problem fixed.
I had the same issue, and the reason was my test class did not have Test at the end of the class name!
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!
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
This article helped me: Empty test suite
Basically I had to create a package - instrumentTest/java - under my src directory, and put all the tests there. Then I could execute these tests individually.
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.
The test class may excluded from the compilation. Fix it in setting-compiler-exclude.
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!
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.
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.
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.
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.
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.
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!!!
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
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.
I know this is silly question, but i am just stuck with this:
1.I have one main project called MainProject.
2. Inside that there is one test project which has its own source and menifest file and in menifest file i added all required to make it test project like this :
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.app.tests" android:versionCode="1"
android:versionName="1.0">
<application>
<uses-library android:name="android.test.runner" />
</application>
<uses-sdk android:minSdkVersion="3" />
<instrumentation android:name="android.test.InstrumentationTestRunner"
android:targetPackage="com.example.app" android:label="Tests for My App" />
</manifest>
Now i right click on it go to "Run As" and "Run Configuration" and select "Android JUnit Test" but it showing error:
MainProject does not specify a android.test.InstrumentationTestRunner instrumentation or does not declare uses-library android.test.runner in its AndroidManifest.xml
Any help plz?
There is one video link of #Lucifer below which is helpful and also my own answer which a link you can check which is also helpful.
Robotium is an Android test automation framework that has full support for native and hybrid applications. Robotium makes it easy to write powerful and robust automatic black-box test cases. With the support of Robotium, test case developers can write function, system and acceptance test scenarios, spanning multiple Android activities.
You can develop powerful test cases, with minimal knowledge of the application under test.
The framework handles multiple Android activities automatically.
Minimal time needed to write solid test cases.
Readability of test cases is greatly improved, compared to standard instrumentation tests.
Test cases are more robust due to the run-time binding to GUI components.
Fast test case execution.
Integrates smoothly with Maven or Ant to run tests as part of continuous integration.
select File/new/project
select Android Test Project
give the Project a name
select test target as the other project you already have, in your posting above "MainProject"
pick the target platform, ie Android 4.0
finish and the test project is made
add classes under src in the test project that extend one of the android.test classes
I am giving answer to my own question,rather it is not a answer it is a link that you can find which is very nice and easy to understand how you can do android unit test using Robotium
Here is the link: LINK