Run tests in parallel (Gradle best practice tip #7)

Tired of waiting around for tests to finish running in your Gradle project? Learn how to run multiple tests at the same time in parallel, saving you precious time.
✔️understand what types of tests are suitable for parallelisation
✔️learn how to configure JUnit tests to run in parallel with the maxParallelForks property
✔️see how this can positively impact build performance in a real-world Gradle project
🚀 FREE QUICK-START GRADLE GUIDE tomgregory.com...
🔥 ULTIMATE GRADLE BUILD BIBLE tomgregory.com...
This is #7 of 30 Gradle best practice tips.

[@purnima2889]

Thank you so much, please continue making such awesome videos

[@TomGregoryTech]

You're very welcome :)

[@ИльясМаметов-и1о]

Thank you Tom

[@Zonab360]

Hello Tom. Do you have any suggestions for running parallel cucumber feature files? I have found resources for running cucumber parallel for maven and parallel for standard test classes with gradle but little on cucumber with gradle

[@juandebenedetti2884]

Incredible your videos! I just had a question... Is this the same as setting the property org.gradle.parallel=true in the gradle.properties file?

[@TomGregoryTech]

Hi Juan. Thanks. Actually org.gradle.parallel is the parallel build feature and different to what's discussed in this video. You can use it to run multiple Gradle tasks in parallel. You can find more info here docs.gradle.org/current/userguide/performance.html#parallel_execution

[@faisaladil5793]

excellent 👏👍

[@chesamirgevara]

Thanks :)

[@OctaviusPelagius]

I think it didn't make much of a difference since the changes to the Gradle build script were not applied. You have the refresh icon active in the top right corner...

[@TomGregoryTech]

Hi Octavius. Good spot!
The magic "Load Gradle Changes" button only affects IntelliJ IDEA, but I'm running the tests from the command line.