Yuki Hamada

@asavill Did you run it from Android Studio or the command line? I downloaded your example project and ran the command, `./gradlew :app:testOnly:connectedDebugAndroidTest --info`, but the test passed and the...

@bilgehankalkan Yes, we are aware of the feature parity issue between Android Studio and Android Gradle plugin. As an interim solution, please use those instrumentation runner arguments. We are actively...

@robpridham-bbc Since Android Studio BumbleBee, it delegates test execution to AGP. So, when you specify orchestrator in your Gradle build file, AS should also use it as long as your...

> "Run Android instrumented tests using Gradle" option was ignored because this module type is not supported yet. Does your project has a dynamic module? If so, we're still working...

Yes, we are aware of this issue and here is our tracking bug: https://issuetracker.google.com/issues/203448784. However, we don't have any progress on it yet.

That sounds like an issue in Android Gradle plugin. I created a separate bug for that, https://issuetracker.google.com/issues/234634397. I'll take a look.

Yes, I agreed that the error message is confusing and doesn't help much. A single APK, self-instrumenting test would simplify the setup. You can enable self-instrumenting tests by setting the...

Thanks for reporting the issue with the detailed explanation. This behavior was by design because moveToState method doesn't work otherwise. However, given the example you explained there are valid use...

> @yuuki3655 > Sorry for leaving this review for these two weeks. > LGTM although I'm not familiar with IntelliJ plugin development because the plugin is kind of isolated from...

Added some integration tests for core workflow for java and updated travis.yaml. Supporting for code coverage needs more work (I tried a bit but it seems we need some special...