Hi im trying to run tests before `assembleRelease` Usually I

Question

Hi im trying to run tests before `assembleRelease` Usually I do it in app build gradle via ``` afterEvaluate assembleRelease dependsOn test ``` However this doesnt work for my multimodule app It seems that code only runs tests in app I could add that block to every module s build file but that is error prone I tried ``` allprojects afterEvaluate assembleRelease dependsOn test ``` ``` What went wrong A problem occurred configuring root project icewarp teamchat android gt Could not get unknown property assembleRelease for root project abc of type org gradle api Project ```

Dominaezzz · Answer

Try `subprojects` instead of `allprojects`

ursus · Answer

``` subprojects afterEvaluate println tasks ``` same as allprojects I dont see neiter `assembleRelease` not `test` in the list

ursus · Answer

< Dominaezzz>

Dominaezzz · Answer

Then where are they

Dominaezzz · Answer

``` afterEvaluate assembleRelease dependsOn app test ```

ursus · Answer

I dont know but they exist I can run them manually I think some evaluation timing is the issue

ursus · Answer

< Dominaezzz> that wont work I cannot see assembleRelease and even if I could youd depend on the app test only

Dominaezzz · Answer

Hmm not sure why this is happening

ursus · Answer

I feel this is stupid anyways there must be a hook into global assembleRelease to run global test task not per module

ursus · Answer

``` allprojects afterEvaluate Run each module s test task after each module s assembleRelease tasks whenTaskAdded task gt if task name == assembleRelease task dependsOn test ``` this works

Dominaezzz · Answer

Wow that s some seriously lazy task config

Dominaezzz · Answer

Glad there s a solution still

ursus · Answer

I was surprised this not being easily googlable but it seems that CIs run simply a command gradlew test they dont care about internal gradle tasks etc

gildor · Answer

It also quite error prone because if you have different flavors it will not run test One problem is that module just don t have assembleRelease it has just assemble for example pure JVM module it will do nothing and test will not be run

ursus · Answer

you can bake that flavor support in the task name string but yea is there a better way this feels needlessly brittle

gildor · Answer

I would use proper task for this

gildor · Answer

that does exactly what you want

gildor · Answer

instead adding it to assembleRelease

ursus · Answer

what do you mean proper task < gildor> how else do you build your releases other than assembleRelease

gildor · Answer

I release using own publishing task and this task depends on `check` task

gildor · Answer

Gradle provides a few lifecycle tasks that do nothing but just hooks for other tasks build assemble check

gildor · Answer

and check is a hook that should be used for all test tasks it s already true for test tasks

gildor · Answer

I don t want to say that there is easy way unfortunately because of more complicated project structure for Android check and test do not exactly what you usually want but I think it s still good rule configure each module in a way that attach different behaviors to lifecycle so before publish you just run check that runs all tasks with tests

gildor · Answer

again it s not something ready to use but I think it s better to be explicit instead implicit convention with assembleRelease task

gildor · Answer

see <https docs gradle org current userguide base plugin html sec base tasks>

ursus · Answer

I might be missing something how do you actually build release if not with assemble lt X gt Release regardless if this is triggered by your custom task or not something still needs to call that

gildor · Answer

build it with a task that runs your tests and runs assembleRelease

ursus · Answer

well thats my point that you need to hardcode or somehow parametrize the assembleXRelease in it therefore you have the same brittleness I think as that x dependsOn test

ursus · Answer

from what I understand you just created customTask dependsOn assembleRelease dependsOn test

gildor · Answer

no

gildor · Answer

you implicitly add those dependencies

gildor · Answer

my point that every module or every type of module knows what should be checked

gildor · Answer

and you explitly run this check test task

ursus · Answer

so root should whitelist all modules tests tasks

gildor · Answer

no every module should run own test tasks

ursus · Answer

well who tells them to run them

ursus · Answer

root test task

gildor · Answer

no

ursus · Answer

then I dont understand

gildor · Answer

when you run `check` it will execute task with this name in all modules

gildor · Answer

not root but every module has own

ursus · Answer

yes prefixless check test

gildor · Answer

this is how Gradle task work

gildor · Answer

yes

ursus · Answer

thats why I meant by root

gildor · Answer

it s bad name for it

gildor · Answer

it s not root root module also may have `test` task

ursus · Answer

okay top level test

gildor · Answer

but when you run task without full path Gradle just tries to run this task in all modules

gildor · Answer

no

gildor · Answer

you probbably don t understand how gradle task execution works

gildor · Answer

gradlew test means please run task with name test in all modules where this task exist UPD And do nothing for modules where this task doesn t exist

gildor · Answer

gradflew module test run task with name test in module with name module

ursus · Answer

well gradle is a mistery most of the time but that I know grinning

gildor · Answer

gradlew test means please run task with name test in root module

ursus · Answer

okay but how can I have test task fail the release task

ursus · Answer

I thought thats accomplished by assembleRelease dependsOn test

gildor · Answer

yes it will

gildor · Answer

every task in graph in case of fail will fail the build

ursus · Answer

okay but in terms of how woukd the task look

ursus · Answer

isnt it chain of x dependsOn y

gildor · Answer

does it make sense which task is fail and order of them

ursus · Answer

not sure what you mean Id fail the task on first error

gildor · Answer

yes this what will happen

gildor · Answer

again I think that assembleRelease dependsOn test is not right approach

gildor · Answer

assemble is just assemble it shouldn t test anything this is the point of this task

ursus · Answer

right but what is the gradle syntax I thought it was assembleRelease dependsOn test

gildor · Answer

assemble on Jvm module doesn t run tests

ursus · Answer

Im not arguing with gradle im mostly bashing it until it works

gildor · Answer

it just assemble project there is `build` lifecycle task which assemble and check the project

gildor · Answer

Yes syntax is correct

gildor · Answer

but Android modules don t have `test` task by default at least as I remember thehy have only testDebugUnit

ursus · Answer

Im confused if you say its correct then whats wrong

ursus · Answer

you say assembleReleade dependsOn test breaks the lifecycle separation thing

gildor · Answer

I m saying that it s wrong approach to add test to dependencies of assemble

gildor · Answer

not a problem of syntax

ursus · Answer

then how should I have test be prerequisite of assembleRelease

gildor · Answer

for example ruse `build` lifecycle task that builds only assembleRelease and run tests

gildor · Answer

This is was my original argument

gildor · Answer

That no need to add dependencies to assembleRelease this task does exactly what it should do

gildor · Answer

at least this is how I see it

ursus · Answer

`build` already does that

ursus · Answer

doesnt build build every type and flavor etc

gildor · Answer

nope but you can implement it

gildor · Answer

gt doesnt build build every type and flavor etc yes most probably this is default behavior

gildor · Answer

you always can have buildRelease

ursus · Answer

Okay but via what syntax if not the dependsOn

gildor · Answer

or something like this

gildor · Answer

I said nothing about syntax

gildor · Answer

I m telling about semantics

gildor · Answer

I also think that it s inccorrect how Android plugin configures graph and add lint as dependency to release task

ursus · Answer

well ``` task buildRelease assembleRelease dependsOn test ```

gildor · Answer

nope

ursus · Answer

is where we started with

gildor · Answer

```task buildRelease dependsOn assembleRelease test ```

ursus · Answer

yea didnt know you could do that thanks

gildor · Answer

just a task that depends on 2 other tasks

ursus · Answer

btw will that work the way you wrote it Since assembleRelease becomes available later in time etc

gildor · Answer

what do you mean are you applying it in allprojects

gildor · Answer

assembleRelease make sense only for application module so it should be configured there

gildor · Answer

you can use afterEvaluate of course

gildor · Answer

I use custom plugins but also it s possible to do using plugin application hooks plugin withType LibraryPlugin etc

ursus · Answer

Well I thought that buildDelease task should be in project level build gradle since its top level or whatever the naming

gildor · Answer

It s possible to do of course

gildor · Answer

we use custom gradle plugins to share any config so it s always explicit

ursus · Answer

Hi < gildor> so I tried it ``` task buildRelease dependsOn assembleRelease test group build description Build release apk for deployment and runs tests ``` If I put that in app build gradle then it builds release however only runs app test not library modules So I tried putting it in project build gradle and I get ``` What went wrong Could not determine the dependencies of task buildRelease gt Task with path test not found in root project icewarp teamchat android ```

ursus · Answer

which I dont understand I see it there

gildor · Answer

Do you really have test task on your root project Does it Android or Java module itself

ursus · Answer

Not sure what you mean its an android project its generated by someone automatically all project seem to have it for me

gildor · Answer

but do you apply android plugin to this module looks that it s your root project

ursus · Answer

no its the root has no plugins

gildor · Answer

so if so you don t have test there

ursus · Answer

yes I do i posted the screenshot

gildor · Answer

This is just idea representation

gildor · Answer

run ` test`

ursus · Answer

``` What went wrong Task test not found in root project icewarp teamchat android ```

ursus · Answer

so where should I put the buildRelease so it works with prefixless `test` I would not expect the task physical location to matter if it references module or prefixless explicitly