This document discusses Android build configuration and testing. It outlines the project structure including unit tests, instrumentation tests, and test flavors. It describes build types for debug, beta, and release and how to add custom configurations. Issues with testing speed and Google Play are noted. Advantages include the modular approach and frequent updates. People are invited to contribute feedback on GitHub.

1. @dggonzalez
+David González

2. Process!

11. project structure

12. testing
!
!
unit tests
instrumentation tests
robolectric
monkey

17. flavours

18. !
!
debug
betaRelease
release
QA

19. buildTypes {
debug {
packageNameSuffix ".debug"
versionNameSuffix "-debug"
}
!
betaRelease {
debuggable false
jniDebugBuild false
signingConfig signingConfigs.arteBetaRelease
}
!
}
release {
debuggable false
jniDebugBuild false
signingConfig signingConfigs.arteRelease
}

20. custom config
!
String tag = createBuildConstant("TAG",
"ARTE_DEBUG")
!
buildConfig syncFrequency, providerAuthority,
suggestionsAuthority, pushVersion, tag,
xitiDomain, xitiSiteId, gcmServer
!
Log.d(BuildConfig.TAG, ”stupid log”)

21. signing

22. !
signingConfigs {
!
}
arteRelease {
storeFile file("../team-props/arteBeta.keystore")
storePassword "arteandroid"
keyAlias "arte"
keyPassword "arteandroid"
}
arteBetaRelease {
storeFile file("../team-props/arte.keystore")
storePassword "THEPASSWORD"
keyAlias "THEALIAS"
keyPassword "THEALIASPASSWORD"
}

23. issues

24. !
testing is slow
no google play console
almost weekly updates
resources merging

25. advantages
!
right direction
Google is working on it
almost weekly updates
flavours
customizable

26. contribute
!
https://github.com/novoda/
AndroidBuildTools/issues
!
https://github.com/novoda/gradle-androidtest-plugin
!
https://github.com/novoda/gradle-androidcommand-plugin

28. ???
@dggonzalez
www.novoda.com/blog
david@novoda.com
+David González