I have a project with three different build types: debug, beta, and release. My test package is always created for debug builds, but QA uses the beta build and we want QA to run these tests on their vast array of devices.
I'm trying to create a testing apk for QA that is signed by the same key as the beta build. Looking through the Android-Gradle documentation, I don't see anything telling me that I can't do this, but I don't see anyway to configure this. Is there anyway I can configure which keystore is used when assembling a test apk? Or is there a way to create an unsigned test apk?
You can now point this to a different target, I don't know when this happened, but from the docs:
Currently only one Build Type is tested. By default it is the debug
Build Type, but this can be reconfigured with:
android {
...
testBuildType "staging"
}
This is an incomplete answer to your question in that it documents what you can't do, but the connectedAndroidTest task, which is what runs the androidTest tests in your project, is hardcoded to run against the debug build type, and I don't see a way to point it at a different build type.
Taking the advice from Is there a way to list task dependencies in Gradle? and examining the task dependency tree, if you run:
./gradlew tasks --all
you get this in your output:
Verification tasks
------------------
app:check - Runs all checks. [app:lint]
app:connectedAndroidTest - Installs and runs the tests for Build 'debug' on connected devices. [app:assembleDebug, app:assembleDebugTest]
app:connectedCheck - Runs all device checks on currently connected devices. [app:connectedAndroidTest]
app:deviceCheck - Runs all device checks using Device Providers and Test Servers.
The documentation for the connectedAndroidTest task claims it runs tests against debug, and the task dependencies (which you see with the -all flag) confirm that the task depends on assembleDebug.
Adding additional build types and flavors doesn't seem to affect the dependency on the built-in debug type.
It's possible that with greater Gradle-fu than mine, you could rewire the tasks to make the tests depend on a different build type, but doing this is likely to be fragile since it's bound to depend on things that aren't supported API in the Android Gradle plugin.
To answer your question most directly, though, if all you want is to run tests against a build with a different certificate, you could change the signing config on your debug build to use the beta certificate:
android {
signingConfigs {
beta {
keyAlias 'key'
keyPassword 'password'
storeFile file('/path/to/beta_keystore.jks')
storePassword 'password'
}
}
buildTypes {
debug {
signingConfig signingConfigs.beta
}
beta {
signingConfig signingConfigs.beta
}
}
}
I tested it and I am able to run androidTest targets against debug builds that use a custom keystore in this way. However, I doubt this solves your problem, because I suspect you want to run your tests against the beta build, not a debug build with the beta certificate.
To add a testing source set for your build variant, follow these steps:
In the Project window on the left, click the drop-down menu and
select the Project view.
Within the appropriate module folder,
right-click the src folder and click New > Directory.
For the directory name, enter "androidTestVariantName." For example,
if you have a build variant called "MyFlavor" then the directory name
shoulbe "androidTestMyFlavor." Then click OK.
Right-click on the new directory and click New > Directory. Enter
"java" as the directory name, and then click OK.
Now you can add tests to this new source set by following the steps above to add a new test. When you reach the Choose Destination Directory dialog, select the new variant test source set.
The instrumented tests in src/androidTest/ source set are shared by all build variants. When building a test APK for the "MyFlavor" variant of your app, Gradle combines both the src/androidTest/ and src/androidTestMyFlavor/ source sets.
Another way is to put following line your in default config.
Currently only one Build Type is tested. By default it is the debug Build Type, but this can be reconfigured with:
android {
...
testBuildType "staging"
}
Related
I want to use firebaseAppDistribution in my project and I want to customize it fo every build type.
I have three buildType debug, staging and release. Each buildtype has a different destination group inside firebaseAppDistribution.
When I run the command to distribute the app on AppDistribute I noticed that group are always missing (but the artificat is correctly uploaded)
I think that the problem is related to how gradle work. I found a post on medium (https://medium.com/#anthony_m_cannon/android-firebase-app-distribution-for-multiple-build-types-4b50ff751ef0) that has the same problem for CI. The author solved it by using an ENV variable and run firebaseAppDistribution outside the buildType scope.
How can I solve in my local environment? Can I discrimante inside build.gradle.kts which buildType is currently running?
Gradle Version 7.6
I have some android instrumented tests under AndroidTests directory in Android Studio. Of course I can manually execute the tests but I need to execute all the tests in the suite after each build ("release" type of build, not during normal debug build). I need to do that because I'd like to validate the new code against the tests before releasing the new app's apk. How to do that? I google it but I didn't find a proper solution yet.
Any idea?
Finally I managed to do that. I have added the following configuration to my build.gradle file in my android studio project:
// execute android tests before realising a new apk
tasks.whenTaskAdded { task ->
if (task.name == 'assembleRelease')
task.dependsOn('connectedAndroidTest')
}
android {
signingConfigs {
release {
keyAlias 'key'
keyPassword 'password'
storeFile file('/path/to/release_keystore.jks')
storePassword 'password'
}
}
buildTypes {
debug {
signingConfig signingConfigs.release
}
release {
signingConfig signingConfigs.release
}
}
After doing that I'm able to run all android tests when building a release apk. If the tests are failing no apk is built.
In general you can define a dependencies for the task using the dependsOn method.
For example:
task A << {
println 'Hello from A'
}
task B << {
println 'Hello from B'
}
B.dependsOn A
You will obtain
> gradle -q B
Hello from A
Hello from B
In your case you can specify:
assemble.dependsOn test
If you would like to specify a dependency only for the release build:
assembleRelease.dependsOn test
Use:
connectedAndroidTest to run the tests on a connected emulator or device.
test to run the unit test on your local host.
I think you should dive in one certain topic: Continuous Integration.
This would allow you to run tests suites after every build or commit, build variants, publish on Google Play and much more... Start with classic Jenkins CI, which may not be the most polished and easy to use, I mean user-friendly tool, but in compare to Travis or Circle CI it provides huge configuration possibilities, nice app community and it's free to use.
Start with this article: http://www.vogella.com/tutorials/Jenkins/article.html
Other tools: I'm already using Travis for my Github projects, but Circle CI or Green House CI might be also good choice.
Hope it will help
I am using Jenkins for CI for my Android Project.
There I am having two build, QA and Dev.
For both some of the configurations are different like url and all which i have in my adroid project.
Now my task is to provide some variable in jenkins, and according to that variable only that apk should be built with required config only. Like if i apply for QA build, so only apk with QA config should be generated.
Is there any way to achieve this?
As far as I understand you have 2 flavors in your gradle file, QA and DEV.
If that is the case you can do that from the configuration of your Job.
In Jenkins go to your Job and then to Configurations
Go to the "Build" section and then to task.
That is a textField where you can define which flavor to compile, for example if you want QA you can define the task:
assembleQARelease
and for DEV
assembleDEVRelease
In the same way you can define if instead of Release version you want the Debug version or if you create any other flavor for your app just Change QA or DEV for this new one.
Also you can add another task before as Clean or even you can define the 3 of them
clean
assembleQARelease
assembleDEVRelease
It will clean the project then create the QA release version and then DEV release.
When I use the 'gradlew connectedCheck' command it always build the debug version and test against the debug version of my app. Is it also possible to test against the release version of my app?
I want to enable proguard and want to make sure that it doesn't filter anything out that is needed during runtime.
You can only test against a single build type right now (though that may change).
To set the build type to test against:
android {
testBuildType "release"
}
You could set this dynamically through a env var to not have to edit build.gradle all the time.
In my Android Studio project I have 2 flavours both having separate corresponding dependencies.
dependencies {
libflavour1Compile project(':TestLib1')
libflavour2Compile project(':TestLib2')
}
Building both of these flavours in debug works great, pulling in their respectful resources.
However, for both flavours debug and release urls are needed. To 'TestLib1' I added strings.xml to the release/res/values folder. Now the build is always inserting this release string to the debug build.
In Android Studio, selecting all build variants to be Debug still results in the release string being used even though the folder is not highlighted.
Creating a Debug build on the command line also has the same result.
./gradlew installLibflavour1Debug
Is there something I'm doing wrong here or do libraries always default to the Release build type?