You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 25, 2019. It is now read-only.
Since AS 0.8.4 they added a new Project View called Android. This view groups all source code under the java folder even if from different flavors or build types. It groups the resources under res and further subgroups like layout and finally the resource name. if different version of the same resource exist it will group them under the resource name. and so on. It will also group manifests and such.
The thing is the test folder disappears under this view. I'm assuming because this view is not expecting it. I'm not sure if your plugin can do anything about it or if we would need the AS team to open an API for us or something.
Otherwise I have to be switching from Android view to Project view to see the tests.
Thanks.
The text was updated successfully, but these errors were encountered:
Just an update, the only reason I haven't started working on this is because the Android project view is only in Android Studio, and you can only debug IDE plugins from Intellij, making this a PITA to test.
here is an idea to add the test source folder to the android project view. It works but I have not much tests done, perhaps it have some bad side effects.
in your build.gradle add the following to the end of android block
But that's the whole point: We do not want to (re-)use the existing androidTest source set as that is often already used for functional / instrumentation tests, and unit tests should be cleanly separated from these. Being able to do so is the main benefit of the android-unit-test Gradle plugin over the official Robolectric Gradle plugin which has this limitation.
Since AS 0.8.4 they added a new Project View called
Android
. This view groups all source code under thejava
folder even if from different flavors or build types. It groups the resources underres
and further subgroups likelayout
and finally the resource name. if different version of the same resource exist it will group them under the resource name. and so on. It will also group manifests and such.The thing is the
test
folder disappears under this view. I'm assuming because this view is not expecting it. I'm not sure if your plugin can do anything about it or if we would need the AS team to open an API for us or something.Otherwise I have to be switching from
Android
view toProject
view to see the tests.Thanks.
The text was updated successfully, but these errors were encountered: