#4673 identified a problem in our testing procedure, namely that we need to do more thorough testing with Proguard enabled.

Right now we have one example: https://github.com/realm/realm-java/blob/master/examples/moduleExample/app/build.gradle#L27 that uses proguard and this is tested during the release process.

This has a number of problems:

• The example isn't run as a release build until after we deployed to Bintray, so any bugs found will require us to either pull the release from Bintray or release a patch version immediately.
• We are not catching bugs during development
• The example does not touch all parts of the code that could be effected by Proguard doing the wrong thing.

It is apparently possible to enable ProGuard when unit testing: https://stackoverflow.com/questions/26482119/android-unit-tests-with-proguard-enabled, but doing so would seriously prohibit normal debugging.

Instead, we should create a special debug build flavor that can be used by CI, so we ensure that all unit tests can be run with ProGuard enabled.