ChatGPT解决这个技术问题 Extra ChatGPT

Gradle build without tests

I want to execute gradle build without executing the unit tests. I tried:

$ gradle -Dskip.tests build

That doesn't seem to do anything. Is there some other command I could use?

Maybe this helps you Gradle Buil without tests
-DskipTests is for Maven
I understand it can be helpful sometimes, but Gradle has easy to enable test concurrency. Maybe shaving 1-2 seconds is not the best thing, so making sure we spend less time running them could allow us to always run tests and not pay for the cost or pay little.

D
David Avendasora

You should use the -x command line argument which excludes any task.

Try:

gradle build -x test 

Update:

The link in Peter's comment changed. Here is the diagram from the Gradle user's guide


This is the correct answer. 'gradle assemble' will leave out many other tasks too. See this diagram to get an idea. For typical real-life builds, 'gradle assemble' will leave out even more tasks.
Link from @PeterNiederwieser no longer valid. Probably he was referring to this diagram: gradle.org/docs/current/userguide/img/javaPluginTasks.png
Works though you may need to add e.g. -x integTest and so on, so not as convenient as Maven’s blanket -DskipTests.
@c_maker, How to perform this from eclipse?
By the way, you can exclude not all, but the certain module's (i.e. for module1) tests using next syntax: gradle build -x :module1:test
P
Paul Verest

Try:

gradle assemble

To list all available tasks for your project, try:

gradle tasks

UPDATE:

This may not seem the most correct answer at first, but read carefully gradle tasks output or docs.

Build tasks
-----------
assemble - Assembles the outputs of this project.
build - Assembles and tests this project.

As an additional hint in case you are debugging your unit tests: gradle assemble will not compile the main files. If you work in getting your unit test fixed then you need gradle assemble testClasses — I think that the build task naming is quite confusing.
G
Guisong He

You can add the following lines to build.gradle, **/* excludes all the tests.

test {
    exclude '**/*'
}

This is nice because I can do this in IntelliJ easy and not command line.
Unfortunately by doing this, it won't be possible to execute any test in IDEA.
@NikolaMihajlović you can wrap the exclude in an if(....) block ei. (in production only)
J
Jacek Laskowski

The accepted answer is the correct one.

OTOH, the way I previously solved this was to add the following to all projects:

test.onlyIf { ! Boolean.getBoolean('skip.tests') }

Run the build with -Dskip.tests=true and all test tasks will be skipped.


For me this is still the only working option as the -x test seems to only work on the starting project but not for dependencies in a multi project build (tested on gradle 2.1). Put the test.onlyif ... in a configure(subprojects.findAll {javaProjects.contains(it.name)}) {} block in your root build.gradle and it will work for all projects.
S
Sahil Chhabra

Every action in gradle is a task, and so is test. And to exclude a task from gradle run, you can use the option --exclude-task or it's shorthand -x followed by the task name which needs to be excluded. Example:

gradle build -x test

The -x option should be repeated for all the tasks that needs to be excluded.

If you have different tasks for different type of tests in your build.gradle file, then you need to skip all those tasks that executes test. Say you have a task test which executes unit-tests and a task testFunctional which executes functional-tests. In this case, you can exclude all tests like below:

gradle build -x test -x testFunctional

D
David Newcomb

Using -x test skip test execution but this also exclude test code compilation.

gradle build -x test 

In our case, we have a CI/CD process where one goal is compilation and next goal is testing (Build -> Test).

So, for our first Build goal we wanted to ensure that the whole project compiles well. For this we have used:

./gradlew build testClasses -x test

On the next goal we simply execute tests:

./gradlew test

Does ./gradlew build testClasses -x test just build testClasses? or does it build regular classes too? Do you need to run both ./gradlew build testClasses -x test and ./gradlew build -x test
@red888 The build builds regular ones while testClasses build test ones. You can check the different tasks here docs.gradle.org/current/userguide/java_plugin.html
P
H
Henrik Aasted Sørensen

Reference

To exclude any task from gradle use -x command-line option. See the below example

task compile << {
    println 'task compile'
}

task compileTest(dependsOn: compile) << {
    println 'compile test'
}

task runningTest(dependsOn: compileTest) << {
    println 'running test'
}
task dist(dependsOn:[runningTest, compileTest, compile]) << {
    println 'running distribution job'
}

Output of: gradle -q dist -x runningTest

task compile
compile test
running distribution job

Hope this would give you the basic


please send a screen shot of the page. i dont know where to put this line of code....
This piece of code should go in your build.gradle :)
S
Sergey Yakovlev

the different way to disable test tasks in the project is:

tasks.withType(Test) {enabled = false}

this behavior needed sometimes if you want to disable tests in one of a project(or the group of projects).

This way working for the all kind of test task, not just a java 'tests'. Also, this way is safe. Here's what I mean let's say: you have a set of projects in different languages: if we try to add this kind of record in main build.gradle:

 subprojects{
 .......
 tests.enabled=false
 .......
}

we will fail in a project when if we have no task called tests


A
Arnau Sistach Reinoso

In The Java Plugin:

$ gradle tasks

Build tasks
-----------
assemble - Assembles the outputs of this project.
build - Assembles and tests this project.
testClasses - Assembles test classes.

Verification tasks
------------------
test - Runs the unit tests.

Gradle build without test you have two options:

$ gradle assemble
$ gradle build -x test

but if you want compile test:

$ gradle assemble testClasses
$ gradle testClasses

d
d4vsanchez

Please try this:

gradlew -DskipTests=true build


@KirankumarDafda - no. You can post an answer whenever you want, even if an existing answer had been accepted. The new answer might be better than the accepted answer, or solve it a different way, or otherwise help others. From Review.
@WaiHaLee I cannot able to edit my comment, but as I got suggestions for new users, I wanted to explain that try to add answers with more clarifications so other user can check if why this answer or code is helpful to them.