Android support

[vanniktech]

I was trying to add this one to an android project and Gradle fails.

./gradlew pitest
Parallel execution with configuration on demand is an incubating feature.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':module'.
> The 'java' plugin has been applied, but it is not compatible with the Android plugins.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Are there any plans on supporting android?

[szpak]

It's the same issue as #24. Do you also use robolectric-gradle-plugin or something else?

Update 2016

There is a @koral--'s version of that plugin for Android. It seems to work fine and it is recommended for Android-based projects.

See: https://github.com/koral--/gradle-pitest-plugin

[vanniktech]

You don't need that plugin anymore. At least it's no longer mandatory. Google guys have recently launched Java Unit Tests for Android projects, so that can be used. So you only need to include the dependency testCompile 'org.robolectric:robolectric:3.0'.

From the command line you can ./gradlew clean test for executing the tests. The task itself is however named test<Module+Flavor>UnitTest

[szpak]

Thanks for the information. I suspect that it also uses JavaBasePlugin instead of JavaPlugin which is not very feasible to support both in the same code base. Nevertheless it is not hopeless, so I will probably give it a shot (one day). Votes from other Android developers willing to use PIT in their project could make that day sooner :).

[emartynov]

Also interested to try

[mdhornet90]

Definitely interested.

[gdaolewe]

Also interested, mutation testing is a great concept that issues like this have always kept me from using in any project.

[JosephYao]

Definitely interested.

Very interested

[Endran]

Me as well!

[vanniktech]

@szpak what's the state of this, since the creation of this issue quite a few others are interested in this

[szpak]

I'm not an Android developer. Is this the only recommended way of testing that would be good to be supported?

@szpak The document you linked appears to be very old. Look here for more up to date references about testing in Android

[xgouchet]

Really interested about this as well !