Fixed
Status Update
No update yet.
Comments
uc...@google.com
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.
be...@google.com
Lucas - I though we ignore the runner from run configurations nowadays?
ls...@google.com
That should be the case, at least for recently created projects.
My guess is that this is an old project, created when it was still possible to choose the runner from the run configurations and that's why it appears in the xml.
#1, could you confirm with which version of Android Studio this project was created (or modified)?
My guess is that this is an old project, created when it was still possible to choose the runner from the run configurations and that's why it appears in the xml.
#1, could you confirm with which version of Android Studio this project was created (or modified)?
ra...@gmail.com
Project was created in 2.2.3 and modified in next versions till 2.3.2 including. Then I started to use 3.0 Canary (1,2,3,4).
I assume this because project created on 14.02.2017 (2.2.3) and I switched to 3.0 after Google I/O 2017.
Dates and versions was taken from here:https://developer.android.com/studio/releases/index.html
I assume this because project created on 14.02.2017 (2.2.3) and I switched to 3.0 after Google I/O 2017.
Dates and versions was taken from here:
ls...@google.com
It makes sense. So what's happening is that in previous versions of Studio (e.g. 2.2.3) it was possible to define the instrumentation runner in the run configuration, but since it was causing conflicts with the one defined in the gradle files, we removed that option, but projects created before it have the option in the xml of the run configuration.
@Michal, should we stop considering at all this option in the runconfig (under the price of possibly breaking some projects created before)?
@Michal, should we stop considering at all this option in the runconfig (under the price of possibly breaking some projects created before)?
Description
AI-171.4101728, JRE 1.8.0_112-release-736x64 JetBrains s.r.o, OS Windows 7(amd64) v6.1 Service Pack 1, screens 1366x768, 1920x1080
I've changed testInstrumentationRunner to custom one, but there was an old runner in .idea/workspace.xml. Error:
>Started running tests
>Test running failed: Unable to find instrumentation info for: >ComponentInfo{ru.codingworkshop.gymm.test/android.support.test.runner.AndroidJUnitRunner}
>Empty test suite.
As we can see the runner haven't changed. After deletion of .idea/workspace.xml test runs successfully.