Hey folks, We just released a new version of Jake's gradle-android-test-plugin....adding better IDE support for running Robolectric tests: https://groups.google.com/d/topic/robolectric/xsOpEwtdTi4/discussion
This is working pretty well for a TDD workflow, except however when we run a JUnit test (whether it uses Robolectric's test runner or not), we pay the penalty of invoking gradle to build, which takes several seconds even when nothing has changed. This doesn't seem too bad maybe, but when you are running single tests or test suites all day long, it adds up. It would be really nice if running these "plain old" JUnit within an IDE did not invoke any gradle tasks. Based on other discussions in this group[i.e. 1,2], it sounds like "plain old" JUnit support within the same module is planned for the Android gradle plugin some time in the future. So, presumably our plugin is a temporary workaround; in the future it seems (with just the android gradle plugin) we would be able to run Robolectric tests alongside Android tests in the same IDE module, with a different source set. Can someone validate this? If so, will it be possible to skip gradle when running JUnit from the IDE? Any idea of when this might happen? -Terry & Mike [1] https://groups.google.com/d/topic/adt-dev/q62wePcjK7o/discussion [2] https://groups.google.com/d/topic/adt-dev/Y8-ppkWell0/discussion -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
