It is a vanilla project generated by the project wizard of Android Studio, with one 'hello world' activity. One is the main application module ('app'). The result for other combinations may be vary. This project is developed under Android Studio 1.3.2, with Android Gradle Plugin 1.3.0, on OSX 10.10.5. Then the unit tests should be immune to the problem. Then add the following line to your adle file: apply from: 'adle'Ĭlean build the system again. Quick startįor those who can't wait to solve the problem, copy the file adle to your module directory with problem.

This project demonstrates the problem and propose a solution. However, it does not take into account that the Java resources may be in dependent modules of the same project. It copy the Java resources from test source set to the class directory. In the issue tracker discussion of Android Studio, an interim solution is given. It does not affect the execution of test cases with Gradle (in Android Studio or command line). This issue affects non-Android unit test and Java resources, executing on Android Studio with 'Unit Test' configuration only. getResourceAsStream( 'path/to/resource.txt') So the following code will fail (return null) in unit test even when it is OK in real world. Simply speaking, when executing (non-Android) unit test in Android Studio, the non-Android resources in Java modules will not be available. This is a demonstration of a known issue of Android Studio as specified here.

Hello world android studio github