Fixed
Status Update
Comments
ls...@google.com <ls...@google.com> #2
Do you have a repro project that you could share with us?
There should be no need to excluding any dependencies: we automatically remove them from the test APK if they are in the main APK.
There should be no need to excluding any dependencies: we automatically remove them from the test APK if they are in the main APK.
ls...@google.com <ls...@google.com> #3
Bug fixed in commit 6e3541c by hiding the UI components related to the instrumentation runner when running a Gradle project.
Description
supply all required information.
Studio Build: 2.3 Preview 1
Version of Gradle: 2.14.1
Version of Java: 1.8.0
OS: Linux
Steps to Reproduce:
1)
- Add android.support.test.runner to the dependencies of the project
- Create a new Android Instrumented Test run configuration -> in the field "Specific instrumentation runner" paste "android.support.test.runner.AndroidJUnitRunner"
- Run it
- Result: you get a "Test running failed"
2)
- Besides the steps in 1) add the line: 'testInstrumentationRunner "android.test.InstrumentationTestRunner"' in defaultConfig in gradle.build (module) file
- Run again
- It works
So, apparently if we set different runners in gradle file and in the test run settings it doesn't work (if we don't set in gradle file, a default one is chosen). In this case, it doesn't make sense to keep the "Specific instrumentation runner" field, since it must always be the same as the class defined by gradle.