Robolectric says "AndroidManifest.xml not found"

Question

While trying to get Robolectric RC3 to work in Android Studio, I get

Caused by: java.lang.RuntimeException: build/intermediates/bundles/debug/AndroidManifest.xml not found or not a file; it should point to your project's AndroidManifest.xml
at org.robolectric.manifest.AndroidManifest.validate(AndroidManifest.java:120)
at org.robolectric.manifest.AndroidManifest.getResourcePath(AndroidManifest.java:469)
at org.robolectric.manifest.AndroidManifest.getIncludedResourcePaths(AndroidManifest.java:475)
at org.robolectric.RobolectricTestRunner.createAppResourceLoader(RobolectricTestRunner.java:479)
at org.robolectric.RobolectricTestRunner.getAppResourceLoader(RobolectricTestRunner.java:471)
at org.robolectric.internal.ParallelUniverse.setUpApplicationState(ParallelUniverse.java:73)
at org.robolectric.RobolectricTestRunner.setUpApplicationState(RobolectricTestRunner.java:421)
at org.robolectric.RobolectricTestRunner$2.evaluate(RobolectricTestRunner.java:234)

I tried

@Config(manifest = "app/src/main/AndroidManifest.xml", constants = BuildConfig.class, sdk=21)

and I tried setting the manifest location in my TestRunner, nothing worked. In the file system I see that the manifest is in

./app/build/intermediates/manifests/full/debug/AndroidManifest.xml

not in the location Robolectric is looking for it. At one point the manifest just got ignored, then a similar issue occurred for resources, the app or Robolectric couldn't find a raw resource my app uses. This is in my build file:

   sourceSets {
    main {
        java.srcDirs = ['src/main/java']
        resources.srcDirs = ['src/main/res']
    }
    test {
        java.srcDirs = ['src/test/java', 'src/main/java']
        resources.srcDirs = ['src/test/res', 'src/main/res']
    }
}

How do I tell Robolectric where to look for a manifest, and more importantly, where to look for resources?

Edit: I have checked out Robolectric from github, I've built it, installed it in my local .m2 repo, the gradle file now refers to the local SNAPSHOT build, and I made sure Gradle doesn't get a new version from a remote repo. Then I copied the RobolectricGradleTestRunner to my project, I have changed the lines where the file locations are defined: it didn't contain the module name. Now it works.

J.C. Chaparro · Accepted Answer · 2015-06-18T16:54:37.003

73

I'm assuming you're trying to run the tests with JUnit. You can try two different things:

Create a Custom TestRunner class, as shown here. Check the CustomTestRunner section, where you basically create a TestRunner that actually knows the right manifest to use. Specify your tests for them to run with your test runner, with the @Config annotation.
(My preferred choice) Go the your JUnit configuration, Run > Edit Configurations. Notice the 'Working Directory' textbox. Append /app (for OSX and Linux) or \app (Windows), to the path written in the textbox. Try running again and it should work.

edited Jun 18 '15 at 16:54

answered Jun 18 '15 at 14:49

J.C. Chaparro

1,079
10
13

This is the new version of the post suggested https://www.bignerdranch.com/blog/triumph-android-studio-1-2-sneaks-in-full-testing-support/ – Jorge E. Hernández Jun 18 '15 at 16:40
3

Yes, adding the "app" string turned out to be essential. – Christine Jul 09 '15 at 23:56
Thank you big time Chaparro! – Leo supports Monica Cellio Aug 24 '15 at 13:36
Thanks for saving me so much time! – Ari Oct 23 '15 at 14:14
13

A better solution is to just set the Working directory to $MODULE_DIR$ as recommended on the Robolectric Getting Started page, http://robolectric.org/getting-started/ – Matt Accola Nov 12 '15 at 14:41
4

What to do if you're using CI? – Oliver Dixon Mar 16 '17 at 08:13

score 66 · Answer 2 · answered Aug 19 '15 at 05:58

66

Same problem on Android Studio. I've solved this problem to edit the configuration of Unit4. you can follow these things.

On Android Studio.

Edit Configurations
In Junit, you have to change the working directory to $MODULE_DIR$.

The important thing is $MODULE_DIR$.

you can reference the following screenshot. thanks.

answered Aug 19 '15 at 05:58

Rooney

1,195
10
18

2

This is the correct answer. It is an issue that affects Mac users. This is actually documented on the Robolectric Getting Started page, http://robolectric.org/getting-started/. – Matt Accola Nov 12 '15 at 14:40
I'm new in Robolectric; just setup the project and probably did something wrong. Still, this answer resolved my issue on Windows. – pepan Feb 14 '16 at 22:31
But why AS need it to every new test ? Is it any way to Indicate "Working directory" for all tests? – Vladyslav Ulianytskyi Jul 04 '17 at 14:11
I don't know why based on other comments it should work but I can not get it working on AS 3.5. Anyone else facing the same? – HBB20 Sep 02 '19 at 00:08

score 9 · Answer 3 · answered Nov 07 '17 at 21:54

9

In case you are still getting this error with Android Studio 3.0, please be sure that your gradle configuration has these parameters:

android {
    ...
    testOptions {
        unitTests {
            includeAndroidResources = true
        }
    }
}

answered Nov 07 '17 at 21:54

busradeniz

317
3
6

Many thanks! That saved my day! I was really struggling with new gradle plugin 3.0.0, gradle 4.1 and Android studio 3. My Robolectric tests went nuts! Now everything is back to normal. – Nunes D. Nov 13 '17 at 19:29
Thank you. This saved me possibly hours of debugging. – rickchristie Feb 23 '21 at 07:22

Kirill Vashilo · Answer 4 · 2015-11-25T09:46:47.587

6

I have faced same errors, We used several flavors and buildtypes So, there are steps to make it working:

Android studio tests run configuration

You have to set working directory to $MODULE_DIR$ in Windows too. http://robolectric.org/getting-started/ should say that.

Unit test should be annotated like this:

@RunWith(RobolectricTestRunner.class) @Config(constants = BuildConfig.class, sdk = 21, manifest = "src/main/AndroidManifest.xml", packageName = "com.example.yourproject") public class SomeFragmentTest {

edited Nov 25 '15 at 09:46

answered Nov 25 '15 at 09:00

Kirill Vashilo

1,559
1
18
27

3

Make sure you are importing the correct BuildConfig - I wasn't paying attention and pulled BuildConfig from a library which causes a similar issue to the OP. – carlrice Dec 16 '15 at 21:44

score 2 · Answer 5 · answered Jan 07 '16 at 21:42

2

Note that intellij 16 EAP has a bug around this $MODULE_DIR$ variable (it's pointing to the wrong place), causing the tests to fail with this exception. See https://youtrack.jetbrains.com/issue/IDEA-149802#tab=History. Should get fixed mid Jan 2016.

answered Jan 07 '16 at 21:42

sakis kaliakoudas

2,039
4
31
51

score 2 · Answer 6 · edited Mar 04 '20 at 06:11

Please find the below steps which resolves all the issues. Step 1: use the version in dependencies

testImplementation"org.robolectric:robolectric:4.0" in app.gradle

step 2: In app.gradle inside android use below

testOptions {    
    unitTests {    
        includeAndroidResources = true      
    }    
}

step 3:in gradle.properties paste the below

enableUnitTestBinaryResources=true

It works !!!

Teja Nandamuri · Answer 7 · 2015-06-18T14:26:06.100

You Can refer the same issue here:https://github.com/robolectric/robolectric/issues/1648

You should mention this in your test code:

@Config(manifest = "src/main/AndroidManifest.xml", emulateSdk = 18)

This tells the robolectric where your manifest file is. This should work unless you change your directory values.

also try to use the template available on the internet.Everything is setup in there.You don't need to change your directory values. You can get it from here:https://github.com/robolectric/deckard-gradle

Edit: The way i see is the exception occurs at "build/intermediates/bundles/debug/AndroidManifest.xml " but you are saying the file is at "app/build/intermediates/manifests/full/debug/AndroidManifest.xml",I guess these two are different locations. Please make sure you have the xml file at build/intermediates/bundles/debug/AndroidManifest.xml "

I did. Didn't work. Also, in Robolectric RC3 it's "sdk=18", not "emulateSdk=18". — Christine, Jun 18 '15 at 14:19
I don't put the xml file in the build directory. The build process does that. — Christine, Jun 18 '15 at 14:32

score 0 · Answer 8 · answered Jul 08 '15 at 22:28

That's correct @Christine. I am also facing the exact problem. And the thing is build process is not creating bundles folder at all under intermediates. And custom robolectric runner also didn't work. Here is the custom runner I used. I haven't still figured out the solution but it seems that the problem may be related to build tool version that needs to used.

[Update] Changing working directory in my unit test run configuration to point to the module root directory which is being tested worked for me.[Update]

score 0 · Answer 9 · answered Aug 29 '17 at 05:52

I had this error after I updated AndroidStudio to 2.3.3 and my gradle plugin was updated too. It was solved by setting working directory to $MODULE_DIR$ and also updating robolectric dependency from testCompile 'org.robolectric:robolectric:3.0' to testCompile 'org.robolectric:robolectric:3.4.2'.

Note that setting working directory while robolectric version is old won't resolve it.

Robolectric says "AndroidManifest.xml not found"

9 Answers9

Linked